What are you talking about? That doesn't make any sense.

Could be a small chance, but it has already made many engineers reconsider their AI stance.

[0] https://www.tunetrackersystems.com/

[1] https://rbr.com/tunetracker-ditches-beos-haiku-for-mac-backb...

The last time we got an OS that was as purely desktop-end-user-oriented with no competing influences was Classic Mac OS, which had serious technical issues.

I get why Haiku does not want to deal with it do this is not a criticism. But I have also used AI to port software and create drivers. Others may not have the ability, even with AI. Perhaps I have docs you don’t. And some of it took a reasonable amount of money and time. I am not going to dedicate that to everything I might use if it was available. And in addition to wasting duplicated money and time, we are destroying the earth recreating things others have already done.

I use Chimera Linux and I have thought about starting a repo just for the stuff that I have ported.

I am not sure what the exact answer is but I hope this is something we figure out.

I looked at the Haiku slideshow and I'm not seeing this. It looks like an eye sore, desktop environments familiar of the 90s. Even early OSX is a massive improvement (as it was to the NeXT desktop).

I worked on a Elektron MachineDrum firmware fix that corrected the MIDI jittering due to incorrect ISR configuration. MD itself is pretty tight already with its RTOS but the fix brought it down to microseconds. I was pretty proud of it because it solves a few phasing problems.

I then turned this over to a friend running a lot of Elektron boxes, and his reaction was, "you mean the sound we've got is wrong? how strange!"

So while I feel the same urge to have ultra tight MIDI timing, I doubt this would be a general interest of the non-technical musicians out there.

And Haiku blooms like heather

New flowers emerge.

Also: Open source is about relationships.

Reviewing code sucks. However at least reviewing code from humans allows you connect and learn from each other. You get to mentor someone. Build a relationship and trust. They learn and grow and maybe someday can also review other people's code.

Nowadays with lots of low effort merge requests and spam it is already easy to burn out. Now add AI. Yeah, no. Why should anyone review AI slop for free. Why? It is the prefect solution to burn your contributors out.

I think the ACPI issue is long standing, but I can't find my bug report anywhere in Trac. I'm fairly sure I've made at least one report, I created my Trac account roughly 6 years ago. But I also remember running into issues with Trac, so maybe it never went through.

What is interesting, FreeBSD last time I used it, had far ,pre simple predictable kernel OOM killer. Anyway, I always either switch off swap on Linux machines or install EarlyOOM.

> There is no reason you can't produce high-quality code with AI conformant to your style guidelines and structural preferences, it just takes a lot more effort than the slop.

It's not just code though. There are humans who deliberately and actively use AI slop to spam people. I saw this first on gobolinux, then on prawn, then on the ffmpeg mailing list. There are really good reasons why many humans dislike the proliferation of AI slop spam.

> Haiku in particular is a very low-velocity project and AI could help them so much

I am not entirely certain about that. If AI were to work so well, Haiku-AI could have already been insta-spawned and auto-fixed everything. Clearly this does not work, so I am unconvinced that AI is the final solution to everything - at the least right now.

What is also unfortunate about Haiku is that things such as ruby do not work by default. Ruby even works on windows, though on Linux it is much more convenient to use.

Linux, however, rarely crashes on a desktop, and when it does, it is usually due to a graphic card driver that doesn't want to work there.

I'm not at all trying to be overly critical or pissy; I'm genuinely curious as to why this is always the gain that AI brings as though it matters (or, rather, this is how it's always stated in one way or another). So I come from a place of confusion when asking this. Why should I care if you can write 100000 or 1000000 lines of code and push out 10 billion commits per minute? (Yes, I am intentionally exaggerating here to prove a point.) If anything, I would argue that increased velocity just brings about recklessness and unnecessary churn instead of accomplishing anything useful.

I have been looking forward to running Haiku as a daily driver for years. And it is almost there. It may even be good enough now for many people. Modern browsers really help.

But I was amazed recently when I put Haiku on an old laptop that was already running Linux. I remember Haiku being so lean and fast and multi-tasking so smoothly. But honestly Linux felt faster on this machine. The memory usage was about the same (a real shock to me). And I missed being able to use containers. So, I ended up putting Linux back on.

This bummed me out because I have been a Haiku fan forever and it has never been better. But when I tried to use it, I could not convince myself there was any benefit (other than diversity). And the reason had nothing to do with applications or drivers.

If all submissions were high-quality, it would probably work. But that is probably unlikely.

Maybe the project could host a searchable directory of AI contributions hosted at external GitHub repos or something.

https://github.com/rcarmo/haiku-arm64-build#haiku-arm64-buil...

This feels to me as the real bottleneck in general. Maybe along with thinking through what to code/prompt.

I don't need more tokens or automated generation of PRs, I'm already at capacity for the care and understanding I want to have for code I own.

I think there's other opinions around AI use there as well, but I'll back off from that. I didn't mean for my post to become top voted, when we should be celebrating Haiku reaching Beta 6. I'm just disappointed that for me, R1/b6 has been a very big regression, right at a time when I've been using AI to make all the software I write cross-compatible with Haiku via Go & SDL, and even use AI to write drivers so more of my hardware works on Haiku... and instead, now I can barely even boot the system.

Your clever, veiled slight, well played.

I tip my fedora.

IIRC you can even configure custom colors, have dark mode, etc. It might look dated with the gray color scheme but that's really the only thing I can guess would look dated to someone.

But, I have seen BSOD multiple times, it’s just that I could trace the problem pretty easily, to something like IRQ interrupts and faulty hardware, MB needs to be replaced, bad driver needs to be downgraded, things like that. And it used to happen a lot more often.

Overall, I just think XP and NT kernels kind of solved this, in large part, by improving the system logging, sys internal tools, adding system restore, etc

On my MacBooks, however, whenever I get the beach ball, I rarely have any idea what to do, and have reinstalled or changed random hardware multiple times.

So yeah, I’ve had my share of problems with all systems, and worked in different environments, but personally I have rarely seen BSOD compared to all the other issues.