HI version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
88% Positive
Analyzed from 1518 words in the discussion.
Trending Topics
#haiku#linux#code#team#desktop#more#windows#used#kernel#system
Discussion (36 Comments)Read Original on HackerNews
In my case, my ThinkPad X1 (Yoga 3rd Gen) used to boot despite what appeared to be kernel panics, but typing "continue" at the kernel prompt would skip past them and everything would then work fine. In Beta 6, it now hangs at boot instead with no kernel panic warning. Disabling ACPI in the safe mode options gets me past that, and there's a way to disable ACPI permanently at boot via some configuration files - though obviously that isn't desirable.
It also seems there's been some work on USB Audio (yay!), but it now causes a kernel panic on boot if a Focusrite Scarlett is connected. Turning the Scarlett off avoids the kernel panic. The Scarlett has never officially worked in Haiku, but it at least never used to crash the system. In my case, I've reverted back to the USB Audio Scarlett Haiku driver that Claude Sonnet vibe coded for me, and for me that's working. (I can't contribute that code because of Haiku rules against AI code, but hopefully the humans will eventually find time to hand code it and get it working.)
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.
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.
> 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.
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 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.
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.
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 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).
What are you talking about? That doesn't make any sense.
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.
A new release greets the world
Congrats to the team
And Haiku blooms like heather
New flowers emerge.
Your clever, veiled slight, well played.
I tip my fedora.