What is the motivation for recreating Be? What would you hope to obtain that you cannot just by using, say, a customized Linux Mint?
If it's just historical/nostalgia/challenge, I get it. But people seem to believe there is something else too, and I'd like to know what that is.
Even now, using it feels like the system is bereft of bloat and cruft. It's a system _for the user_ that doesn't assume that the user is technically incapable.
IDK what scheduler voodoo they were doing, but it was awesome.
Only things I've seen that achieved something similar were QNX/Photon, and (though with the benefit of way stronger hardware and a ton of "cheating" by suspending applications) some (mostly early) versions of iOS.
I'm not sure I have any use for Haiku today, but I definitely wish for a world in which computer GUIs didn't feel so damn slow and janky and pre-occupied with whatever it's got going on internally rather than what I need it to be doing right now.
Also, I wish some kind of tagging system for filesystems had taken off well enough that I could rely on it, even cross-platform and when copying files between filesystems. Entire programs could just be file tags. Other programs could just be a thin GUI over tagged files. It sucks that didn't end up becoming a standard and reasonably cross-platform-compatible thing.
Hmm.
When things are coded right, Haiku / BeOS is blazing fast (every single thing runs in a separate thread), and resource usage is tiny. I think the OS only uses about half a gig of RAM? When the apps are coded right, there's a feeling that this is how our modern computers could have been, free from bloated software and using the full speed of the machine. And when shutdown only takes a couple of seconds, it makes you wonder what the other OS's are doing.
Of course the reality is not that. Display drivers & video codecs on Haiku often don't have the right hardware acceleration, most of the software you need is now Linux ports rather than BeOS native. But Haiku sometimes feels like a calming OS. Because it's so small and quite modular, it feels like an OS you can still potentially get your head around.
As I said in another comment, I've only played with Haiku in a VM for not very much time, but I am a huge supporter of operating systems that are willing to break out of the codified mediocrity we've labeled "POSIX"; I suspect that we might be leaving a lot of performance on the table by constantly trying to POSIX compliant all the time.
MacOSX would be really different today if it were based on BeOS instead of NeXT...
So how did they do it? And does Haiku use the same tech under the hood or does it forus on matching the user experience?
On Linux I can use perl, ruby, python, php, julia - you name it. Good luck thinking you can do this on Haiku, as-is.
Edit: I should say that I like Haiku, but I used it many years ago, and the situation with regards to programming still has barely improved here for the most part. They are building literally a dream OS nobody will seriously use.
Then write code to make it work. Complaining about nothing just wastes time.
But I agree on the perpetual beta feeling though, and if you're wanting to get actual work done then Linux is the only way, if you don't want Windows / Mac.
Vitruvian OS: https://v-os.dev/
(https://www.haiku-os.org/legacy-docs/bebook/TheKernelKit_Sys...)
https://github.com/VitruvianOS/Vitruvian/blob/0e4c6e33ab235b...
> Returns the temperature of the motherboard if the computer is currently on fire.
> The following functions, types, and structures are used to convey basic information about the system, such as the number of CPUs, when the kernel was built, what time it is now and whether your computer is on fire.
tier one: linux, windows, freebsd tier two: openbsd, netbsd tier three: haiku tier four: all others
One of the few OSes where my wifi and sound just worked out of the box :)
Its totally usable DESKTOP fOS.
To get it working I have to type "continue" at the two kernel panics on startup due to spurious / overzealous Thunderbolt PCI warnings. I also needed help from an Action Retro video to figure out how to setup the UEFI BIOS files on the correct partitions on the bootable Samsung USB stick I use. But it works enough that I can boot into it straight off USB when I want a break from Windows & Linux. They finally added support for the WiFi in my particular ThinkPad. There's basically no bluetooth support, so if you want a wireless mouse and keyboard, something like the Logi Pebble 2 bundle with wireless USB dongle works well.
Haiku has a Go 1.18 port now that mostly works, so that helps. A lot of Qt software has been ported across, though obviously the ideal would be truly native BeOS software.
The main thing I find Haiku lacks is a decent email client. That really prevents productive work for me. There's Claws Mail, but it has enough bugs that I didn't even find it usable, nevermind reliable. There's also some memory or networking issues they haven't tracked down. When I'm using terminal sessions, network responses often have dropped bytes in the output.
Actually the thing I'm really lacking is Claude Code. I ended up building my own minimal TUI API harness / client on Haiku to try and get work done. Haiku's web browsers (like WebPositive) sometimes have problems with the Claude website. I've been wanting to use Claude to help write more Haiku / BeOS software and fix various OS issues - a couple of weeks ago I used the Claude API and $30 API credit to make a USB UAC 2 audio driver for Haiku that works with Focusrite Scarlett devices (both playback and recording). But Haiku's AI policy means I can't contribute those fixes back. Though I understand their desire to keep the source pure and free from any potential copyright liability concerns, especially as they release it under an MIT license.
If I ever become a billionaire, I'm going to throw a boatload of money into an seL4-based desktop operating system.
lukaslalinsky•1h ago
ranger_danger•1h ago
For the longest time there was not a modern browser that could run, but now there are multiple chromium-based and firefox-based options.
jdboyd•1h ago
throwaway27448•57m ago
MisterTea•27m ago
kouosi•54m ago
efficax•53m ago
shevy-java•36m ago
MisterTea•24m ago
wolrah•31m ago
The x86-32 version (and hypothetically the never-complete PowerPC version), as I see it, exists (or would exist) for binary compatibility with legacy BeOS systems. The AMD64 version on the other hand is a hobby OS demonstrating a path not taken where personal computer operating systems remained separate from server operating systems.
Also, like others, these days I can do basically everything I need to do on a computer other than gaming as long as I have a browser that supports the modern web and a SSH client so Haiku is absolutely fully usable on the right hardware.
fragmede•22m ago