My idea when I installed Haiku was to make my own version of the "old computer challenge"[1], with an emphasis on using GUI apps.
Similarly to @probono (a FOSS dev), I also found Haiku "shockingly good"[2] at being a lightweight, responsive, easy-to-use desktop OS.
After some patching, I was even able to compile Tectonic[3], a modern LaTeX engine written in Rust, and Quaternion a Matrix client supporting E2EE[4]. All that running on a single core Athlon 64 and 1.5GB of RAM.
I posted some screenshots in a Mastodon threads if you are curious[5] (but my posts are in french sorry :/). And of course this comment is posted from Haiku!
[1]: https://dataswamp.org/~solene/2021-07-07-old-computer-challe...
[2]: https://medium.com/@probonopd/my-first-day-with-haiku-shocki...
[3]: https://tectonic-typesetting.github.io/en-US/
[4]: https://github.com/quotient-im/Quaternion
[5]: https://mastodon.tedomum.net/@tgoldoin/109554115997967651
I am absolutely not surprised it works well on Athlon 64.
Maybe I ran BeOS slightly before a demo CD was available, or maybe I just didn't risk burning a coaster. (Remember those days where you had to worry about your OS not being able to feed the CD burner as fast as it was writing?) When I demoed BeOS around 2000, it was on a floppy (I repurposed a free AoL floppy from a few years earlier... by that time AoL was mailing free CDs instead of free floppies). The demo floppy allowed one to format a BeFS partition on the drive, and I think even put the kernel on the drive, but kept the bootloader on the floppy to encourage purchase.
I woke up one morning to see the floppy drive light on, and apparently a BeOS kernel or usespace driver bug caused it to spin the floppy continuously all night without moving the read/write head. I popped out the floppy and pulled back the dust guard to discover a thin stripe where the magnetic media had been polished off of the floppy. The drive didn't read any floppy correctly after that; presumably the read/write head was covered in magnetic media dust.
I don't remember how, but I eventually found instructions for copying the bootloader off of the downloaded floppy image and getting GRUB to find it, so I didn't need to put my replacement floppy drive at risk.
If there is one thing to say about Haiku, their slow and steady approach has resulted in a remarkably solid Kernel and base system. It is extremely light and has a well-built and consistent environment. I've always hoped more engineers would hop on the bandwagon to accelerate development, but what the team has achieved is notable in comparison to other alternative/"hobby" OSes.
Linux is a huge OS by the standards of BeOS and Haiku, with an early-1970s design and layers and layers of legacy cruft between the kernel and the user.
Dr Tanenbaum called it obsolete even 30 years ago: https://www.edn.com/linux-is-obsolete-thread-is-started-janu...
... and he had a point then.
SMB is supported by fusesmb, which is available as a package.
consider sponsoring the team here: https://github.com/sponsors/haiku
The only thing that Be did have was one nifty demo, and a somewhat innovative file system. Apple must have correctly deduced that it would be easy to improve the filesystem, because they later did so, with the same author.
Comparing BeOS and NextSTEP in 1997 is like comparing a ham sandwich to a piglet and a bag of flour. One of these things was a finished product.
As much as the original BeOS network stack was mediocre (and it was, it wasn't fixed until the BONE design in that final Dano leak in 2001) the much-touted NeXT networking stack was literally the open source 4.3BSD networking code running hosted, with their awful NetInfo system on top, which Apple spent the next several years excising. Excising like the Adobe license fees cost more than a PC, few major vendors (not even Adobe!) willing to port their software to, Display PostScript GUI they had to throw out and replace.
I'll grant that they got a really good set of development tools they're still essentially using, and Be's were rough (and kind of alien, that kind of pervasive threading is _still_ hard with decades of work on the tooling).
Apple bought NeXT because the stack looked architecturally like a less-bungled version of their own failed Pink/Taligent effort, and Steve Jobs had a better relationship with people still at Apple than Jean-Louis Gassée.
Oh and they got Steve Jobs of course who made quick work of pushing out the old Apple leadership. And good that he did.
BeOS was very light weight. Its ethernet driver for 3c509 was buggy and crashed often, but being a userspace driver, I just got a popup asking permission to restart the driver. Conversely, a couple years later I had an OSX laptop, and a corrupted backup CD that would kernel panic OSX, Win2k, and Linux. (Honestly, ISO 9660 and FAT32 drivers should be migrated out of mainstream OS kernels, since kernel latency is very far from being the bottleneck when using thunmb drives or CDs.)
On the other hand, BeOS had some questionable uses of metadata. After improperly using tar to backup my home directory before a reinstall, I lost all of my NetPositive browser bookmarks. I didn't realize each bookmark was a zero-sized file with the URL actually stored in metadata. My improper backup procedure dropped the metadata fork.
Also, there was a kernel bug related to semaphores. I had some semaphore code that worked fine under Linux but would kernel panic BeOS.
Had Apple purchased Be, we'd likely have a much lighter weight OSX, though perhaps with poorer support for multiple users.
I'm still hoping that someday QNX RTP gets open-sourced. A hard real-time light weight microkernel OS was fun to play around with. In particular, a cache benchmark I ran for a systems class showed quite a bit smaller cache footprint for QNX vs. Debian. (Though, Debian almost certainly had more daemons running, so it's not an apples-to-apples comparison of kernel cache footprints.)
A real shame that they faded out. I kind of miss those days with all the different and varied workstations – Be, SGI, DEC, HP, IBM, Sun, ...
I am continually amazed at how much progress the project continues to garner. It really proves there was something magical to BeOS.
Can we get away from the “leaky bucket” security paradigm where despite all of the best efforts and gradual improvements, prevalent operating systems “keep on giving” in terms of exploits that are discovered all the time. Is there something akin to what Rust is for programming languages?
Or what about an operating system for AIs? Is the current stack of Linux, GPU drivers, and some ML SDK on top an adequate answer for emerging AI applications?
Or if you still believe in Blockchain applications, what about a native OS for that?
And the list goes on.
All I see in Haiku/BeOS is a pretty, albeit dated user interface. Someone educate me what else they bring to the table.
Praising the positives of your work at the expense of the criticism of other's work won't do you any favours.
These days, stippi does not have much time for Haiku, but there are a number of developers & community members who have picked up where he left off, continuing work on the UI and drawing new icons when required.
(Old hands from the BeOS days may remember stippi as the co-developer of the shareware "WonderBrush", which now runs on Haiku and has been open-sourced [3].)
[1]: https://www.haiku-os.org/news/2006-11-03_icon_contest_and_be...
[2]: https://github.com/haiku/haiku/commit/2f86ba45579bdc9648b232...
There's a screenshot tour here: https://www.haiku-os.org/slideshows/haiku-1/
And the release notes, linked from the release announcement, have screenshots: https://www.haiku-os.org/get-haiku/r1beta4/release-notes/
Edit: Fixed typo
Both of them highlight how much nicer a vertically integrated user experience can be as well as how much lighter weight a modern desktop can be as well. They also demonstrate that it does not take dozens of corporate paid engineers to do it ( not that I would turn them away ).
Haiku has a long lead over Serenity in terms of hardware support and now app compatibility ( with the new X11 and Wayland stuff ). That said, having to drag along binary compatibility with BeOS must really be slowing Haiku down at this point.
I am looking forward to using one or both of them in the future.
And this is really where it’s difficult to get any real progress without massive industry backing.
So I’m not sure how either will become a contender for any real word desktop use without someone at the scale of Google putting their weight behind them.
We can merge a change to Haiku's kernel and drivers, and test builds will be available with it on the "nightly" channel within hours. We can issue a patch for the system C library headers, trigger rebuilds of packages from the ports tree against it as soon as CI builds finish. We can send users experimental builds of work-in-progress features for testing, with very little technical know-how required to install such a patch or revert to the previous version if it breaks something.
There are so many huge advantages Haiku has due to how the project is structured that the "Linux desktop", whatever upsides it does possess, basically cannot ever have by its very nature.
So there will never be 3rd party software? Not even a GNU Emacs? Surely you're using GNU GCC, aren't you?
For many people that makes Haiku suitable to run daily.
The lack of a built-in solution for full-disk encryption is also a blocker for me. It's something I keep meaning to try and tackle (say, by porting over OpenBSD's FDE implementation), but I ain't quite comfortable enough yet with Haiku's codebase to even know where to start.
If we get a web browser with advert blocking, it will be ready for the modern web.
This is one the most interesting bits in an already awesome release notes! Haiku would rock with Raspberries and I can't wait to use it as the default OS for family 400s.
The RISC-V port on the other hand is nearly fully usable even on bare metal. I know some people run it on HiFive Unmatched, at least...
>Instead of running a full X server as XQuartz or other X11 compatibility packages do on other operating systems, it directly handles Xlib API calls and translates them into Haiku API calls, instead.
>It is a little more complicated than the one for X11, running an “in-process Wayland server” for each application instead of translating C API calls directly.
Unfortunately the Wayland part has no blog post similar to the X one.
This doesn't look very good, in my opinion. While having working WiFi is important, stacking compatibility layers is not a good architectural decision.
You can certainly dual-boot it on x86 machines, though.
It's just a proof of concept but some people are using it for CI as well [2].
[1] https://github.com/hectorm/docker-qemu-haiku
[2] https://github.com/HaikuArchives/ArtPaint/blob/7f5c49278545e...
Downloads: https://www.haiku-os.org/get-haiku/r1beta4/
I use lightweight linux VMs to keep different workspaces and hobbyspaces separate from my main OS. Depending on how the test goes, I feel that Haiku might replace some of those linuxes.
> but now (thanks to Emacs developers!) has a fully-upstreamed, polished-to-a-shine native GUI.
This alone is definitely worth giving it a go!
It’s slow and a total memory waste, but web became a new UI toolkit that actually solved OS compatibility issues. Who would have thought…
I mean I tried a number of electron apps and always end up using the web version that is always the most up to date and are as wll integrated to the desktop thanks to desktops support for web notifications.
And in many cases, the web version end up more stable/reliable than the electron one. MS Teams is a great example of that.
It's a much more filled-out page, and probably what most people are clicking through to anyways.
I only use if for testing free software packages in a "weird" build environment, but every time I do I feel sad for how much we've regressed in terms of the latency of modern desktop software.
Beyond latency the UIs are also just a lot more useful, the subtle faux-3d delineates the boundaries of control surfaces and make it much more clear where you need to click and what will happen when you do.
I was really waiting for this! I want to install Haiku in an old computer for an old lady friend to use (and for me to see how she will use it). They only problem always was that youtube never really worked. That is the chance!
Show HN: Xlibe – A serverless Xlib (X11) compatibility layer for Haiku - https://news.ycombinator.com/item?id=31167562 - April 2022 (46 comments)
Giving Haiku Beta 3 a try - https://news.ycombinator.com/item?id=29757451 - Jan 2022 (48 comments)
My progress in porting Wine - https://news.ycombinator.com/item?id=29753069 - Dec 2021 (62 comments)
Haiku Now Has Experimental 3D Acceleration - https://news.ycombinator.com/item?id=29390689 - Nov 2021 (71 comments)
Haiku has hired an existing contributor to work on Haiku full-time - https://news.ycombinator.com/item?id=28305191 - Aug 2021 (105 comments)
20 Years of Haiku - https://news.ycombinator.com/item?id=28241255 - Aug 2021 (119 comments)
Haiku Beta 3 - https://news.ycombinator.com/item?id=27955755 - July 2021 (96 comments)
HaikuOS running on RISC-V hardware (HiFive Unmatched) - https://news.ycombinator.com/item?id=27867941 - July 2021 (80 comments)
The Dawn of Haiku OS (2012) - https://news.ycombinator.com/item?id=27616822 - June 2021 (15 comments)
Haiku Monthly Activity Report – May 2021 - https://news.ycombinator.com/item?id=27395511 - June 2021 (20 comments)
Haiku OS ported and running on RISC-V - https://news.ycombinator.com/item?id=27129305 - May 2021 (86 comments)
Haiku Activity Report – January 2021 - https://news.ycombinator.com/item?id=26055781 - Feb 2021 (24 comments)
Haiku: Call for Wallpapers - https://news.ycombinator.com/item?id=24756787 - Oct 2020 (24 comments)
Haiku: Contest for System Sounds - https://news.ycombinator.com/item?id=24593719 - Sept 2020 (15 comments)
A decidedly non-Linux distro walkthrough: Haiku R1/beta2 - https://news.ycombinator.com/item?id=23676975 - June 2020 (46 comments)
Haiku R1/beta2 has been released - https://news.ycombinator.com/item?id=23469209 - June 2020 (254 comments)
Haiku Alpha 1: Rebirth of legend - https://news.ycombinator.com/item?id=22401383 - Feb 2020 (14 comments)
500 Byte Images: The Haiku Vector Icon Format (2016) - https://news.ycombinator.com/item?id=22373422 - Feb 2020 (91 comments)
The Haiku Operating System - https://news.ycombinator.com/item?id=20812877 - Aug 2019 (1 comment)
My sixth day with Haiku: Under the hood of resources, icons, and packages - https://news.ycombinator.com/item?id=20443136 - July 2019 (38 comments)
Most long-standing XHCI (USB 3.0+) issues resolved - https://news.ycombinator.com/item?id=19352839 - March 2019 (58 comments)
Haiku Beta is finally here - https://news.ycombinator.com/item?id=18769814 - Dec 2018 (53 comments)
What makes BeOS and Haiku unique - https://news.ycombinator.com/item?id=18583722 - Dec 2018 (219 comments)
Haiku R1/beta1 has been released - https://news.ycombinator.com/item?id=18099127 - Sept 2018 (79 comments)
The State of Rust on Haiku - https://news.ycombinator.com/item?id=17472907 - July 2018 (84 comments)
LibreOffice is now available for Haiku - https://news.ycombinator.com/item?id=17440862 - July 2018 (157 comments)
Haiku Project - https://news.ycombinator.com/item?id=15973918 - Dec 2017 (64 comments)
Scripting the Haiku GUI with hey - https://news.ycombinator.com/item?id=15697697 - Nov 2017 (47 comments)
Trying to work in Haiku, the BeOS successor - https://news.ycombinator.com/item?id=14697308 - July 2017 (24 comments)
Porting Swift to Haiku - https://news.ycombinator.com/item?id=14617453 - June 2017 (49 comments)
Haiku booting in UEFI mode - https://news.ycombinator.com/item?id=13200633 - Dec 2016 (94 comments)
Haiku Project - https://news.ycombinator.com/item?id=12566056 - Sept 2016 (143 comments)
500 Byte Images: The Haiku Vector Icon Format - https://news.ycombinator.com/item?id=12420763 - Sept 2016 (81 comments)
Haiku OS Action – From BeOS compatible to Desktop [video] - https://news.ycombinator.com/item?id=9713843 - June 2015 (4 comments)
Haiku OS – Fundraising 2015 - https://news.ycombinator.com/item?id=9046701 - Feb 2015 (27 comments)
Whatever Happened to BeOS? - https://news.ycombinator.com/item?id=8175135 - Aug 2014 (17 comments)
Interview with Haiku developer Paweł Dziepak - https://news.ycombinator.com/item?id=7754772 - May 2014 (47 comments)
Haiku meets 9th processor - https://news.ycombinator.com/item?id=6987731 - Dec 2013 (44 comments)
Haiku Operating System - https://news.ycombinator.com/item?id=5564766 - April 2013 (110 comments)
Haiku OS (BeOS clone) - https://news.ycombinator.com/item?id=4123941 - June 2012 (46 comments)
HaikuOS x86_64 port part of Google Summer of Code - https://news.ycombinator.com/item?id=3906710 - April 2012 (15 comments)
The Dawn of Haiku OS - https://news.ycombinator.com/item?id=3904972 - April 2012 (110 comments)
* Haiku Project Announces Availability of Haiku R1/Alpha 2* - https://news.ycombinator.com/item?id=1334827 - May 2010 (11 comments)
Haiku: A Perfect Desktop Operating System? - https://news.ycombinator.com/item?id=1009751 - Dec 2009 (5 comments)
Haiku - https://news.ycombinator.com/item?id=826986 - Sept 2009 (29 comments)
Haiku Project Announces Availability of Haiku R1/Alpha 1 - https://news.ycombinator.com/item?id=820844 - Sept 2009 (20 comments)
Haiku OS first alpha scheduled for September 6th - https://news.ycombinator.com/item?id=767766 - Aug 2009 (11 comments)
BeOS Lives: Haiku Impresses - https://news.ycombinator.com/item?id=475756 - Feb 2009 (19 comments)
If we like it on our pcs
Install and use it
This is pretty neat. Is it something that script-type applications can do, as opposed to more formally-programmed applications?
Or for that matter is there that kind of system scripting language for the OS, like an ARexx for Haiku? I've used Haiku but not at this level.
It detected only 1024x768 when it started up, which made things look blurry; fixed by going into the Screen app and changing it. Haven't figured out the Wifi yet, but the Ethernet was detected and worked immediately. With both Web and WebPositive browsers up and with a page or two loaded, 1.2GB RAM was in use, total, for everything.
9front also uses OpenBSD drivers for Intel cards, so it might also be one