Earlier quoted context omitted.
There are Haiku/BeOS-style window manager/GTK themes if that suits your needs better.
could you point them out? i actually did a search but could not find much. there are GTK themes, but nothing i could find that converts a gnome desktop. stuff is either incomplete or outdated. i actually managed to get half BeOS theme together for KDE, and i still use that on my desktop. but it's inconsistent, and in particular the tab style window management is missing, which is really the best part of the interface…
Haiku R1/beta6 has been released
81–90 of 110 posts
Re: Haiku R1/beta6 has been released
#82Has anyone tried installing Haiku on old mac 2012 intel and older ? How challenging would that be ?
I just so happen to have a 2008 Core 2 Duo MacBook Pro doing nothing. I followed the directions at:
https://www.haiku-os.org/guides/uefi_booting/
and it installed and booted without any issues.
Re: Haiku R1/beta6 has been released
#83Just a heads-up for those trying it out, I've found a couple of regressions in Beta 6 that rendered my Haiku system unbootable, until I remembered about hammering the space key during the boot sequence to get to the safe mode menu. 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…
Haiku should rethink that AI rule. Put very high code quality gates in place, sure, but Haiku in particular is a very low-velocity project and AI could help them so much. 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.
I think the most productive thing is:
1. Read rules about not using AI
2. Reflect upon and understand why they exist
3. Develop software however the f*ck you want
4. Ensure it is high quality
5. Open a PR
6. Don’t tell anyone (i.e. don’t do the things people hate about AI-assisted code)
People are going to get made at this take but come on, we’re trying to build things. Use the hacker spirit. Make things that solve problems.
Re: Haiku R1/beta6 has been released
#84Earlier quoted context omitted.
Don't get me wrong; Mac is light years ahead. What I mean is the level of harmony and design integrity the Haiku has. I doubt that any corporation can ever have even the team that used to make the icons of Tiger/Leopard era. The scrollbars of the Leopard or the whole Aqua. But given their team size and small scale of Haiku; this is one amazing job. The apps, the website, the icons; the documentations... all are in ha…
All of that has been straight copied from BeOS, which was a real corporation worth millions of dollars and in the cutting edge of technology at the time.
Very good point!
Re: Haiku R1/beta6 has been released
#85Haiku could theoretically fill a niche for music production workflows. Ultra tight MIDI timing and sequencing, low-latency audio and a beautiful desktop. I hope this dream comes true eventually.
I doubt this, but hear me out for the reason: 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…
correctness of minor logic details is of general interest to no one, but of substantial benefit to everyone
Re: Haiku R1/beta6 has been released
#86Earlier quoted context omitted.
Velocity of LoC isn't important. Velocity of user visible improvements can matter if a project feeds off of usage and popularity. Or at least that velocity matters until the OS is capable enough to satisfy the user base.
I... Don't agree with this. If your users have followed your projects developments even remotely reasonably, you taking a few months to implement something or to figure something out is not a sign that the project is dead. It would be one thing if your project was completely inactive for like 2-3 years.
Haiku OS has gone up to 6y between releases. While not entirely inactive in that time, lurkers who aren't as motivated to dig for signs of life could reasonably conclude the project is inactive.
For example, I'm a big fan of DOSBox. And while the core project still has some code check-in's from time to time, its last release was 7ya. Now I use and follow forks because they're consistently releasing useful features and fixes.
Re: Haiku R1/beta6 has been released
#87Earlier quoted context omitted.
I imagine that their issue is reviewer bandwidth. 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.
My understanding is that the AI policy is more to do with issues of copyright and code provenance. They want to make sure that all of their code is cleared with no risk of accidentally using 'stolen' code or GPL code repeated by an AI. I can at least understand the policy. 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 sh…
OpenAI at least provides legal indemnification against those claims
Re: Haiku R1/beta6 has been released
#88Earlier quoted context omitted.
I'm curious why velocity is sooooo important. Every single AI discussion that I've read always always always mentions velocity or development speed as though that somehow is the ultimate goal. Why does it matter if your velocity isn't as fast as everyone else? Maybe taking things slowly might actually be a good thing. I'm not at all trying to be overly critical or pissy; I'm genuinely curious as to why this is always…
Velocity of LoC isn't important. Velocity of user visible improvements can matter if a project feeds off of usage and popularity. Or at least that velocity matters until the OS is capable enough to satisfy the user base.
Haiku feeds off the interest and fun it brings to its developers. If you put AI in the mix you can poison what they do for fun and sink the project.
Re: Haiku R1/beta6 has been released
#89Just a heads-up for those trying it out, I've found a couple of regressions in Beta 6 that rendered my Haiku system unbootable, until I remembered about hammering the space key during the boot sequence to get to the safe mode menu. 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…
I think there should maybe be shadow repositories available for Open Source projects where things like your driver could be contributed. 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 go…
You can host an alternative repo, with the packaging system it has it's as easy as on any run-of-the-mill Linux distro. The easiest way is just to store your recipes in a repo (I do that: https://github.com/przemub/haikuports-nonfree) but a binary repo can also be easily hosted. In the hybrid architecture Haiku kernel has, drivers can also be loaded at run time. I think it's a good idea, much better than shoehorning into the main repo.
While people have varying stances, I understand the policy at least for the main Haiku repo code. Allowing AI-written contributions means you will get code that neither the contributor nor the teammembers fully understand, and asking questions about the wider context becomes futile. It would require a lot of distrust to get consistently acceptable results.
I think the fact that there are multiple people who have deep understanding of what they are working on and of the system's structure goes a very long way to establish this trust and ensure quality.
In this environment, I think (as I said, the opinions are varying), having the contributor learn about their contribution (even asking AI as a starting point, if they want to) and then (re-)write it themselves is a really minimum gate to make sure everyone knows what is happening.
Re: Haiku R1/beta6 has been released
#90Haiku could theoretically fill a niche for music production workflows. Ultra tight MIDI timing and sequencing, low-latency audio and a beautiful desktop. I hope this dream comes true eventually.
Tunetracker[0] radio automation software (not sure what else it did/does) started on BeOS, then moved to Haiku. After 25 years(!)[1] it's on Mac now. [0] https://www.tunetrackersystems.com/ [1] https://rbr.com/tunetracker-ditches-beos-haiku-for-mac-backb...
This is sad, because it doesn't run on Haiku anymore, only Mac.