I bought an Amiga in the early 90's and enjoyed it immensely. Commodore went under and Amiga died.
I bought BeOS in the late 90's and enjoyed it immensely like a breath of fresh air in a sewage pipe. BeOS died.
With my track record I really, really should've bought Windows. Twice, to make sure.
MarsIronPI 3 minutes ago [-]
[delayed]
conception 3 hours ago [-]
Correction, BeOS was killed. I’ll never get over Microsoft getting in trouble for including a browser in Windows but not for forcing companies to not allow BeOS to be installed when it was getting legs.
limagnolia 1 hours ago [-]
I studied the MS antitrust case extensively when it was happening, and I agree that the abuse against BeOS was MS greatest antitrust offense. However, as a fan of BeOS, I see no evidence at all that Be Inc. would have been successful if MS hadn't abused its position. Unfortunately we will never really know what might have been.
tvaughan 27 minutes ago [-]
OS/2 Warp was out before Windows 95, and better.
pjmlp 10 minutes ago [-]
If we ignore the fact that it required 1000 euros more in additional hardware, thus most folks went with DOS/Windows 3.x instead, and when Windows 95 came around it was already too late for adoption.
erremerre 4 hours ago [-]
I am in the same boat, every time I like something, it is a commercial failure. They should really hire me to check if I like whatever project they got in mind and if I do, cancel immediatetly and save the losses from being a failure.
They should have me do that with television programs.
chocochunks 4 hours ago [-]
I think I did this with phones. WebOS, BB10, Windows Phone 7 & 8. All dead lol.
BirAdam 3 hours ago [-]
I was Palm guy and not Blackberry, so I went from a Palm Treo to webOS. After that though, I went to iPhone. I considered Windows Phone though. The tiles and text orientation were so amazing. I am, however, glad that I never went down that road, not just because Windows Phone died, but also seeing what has happened to Windows more recently.
This post is really bringing me back! I knew talk of BeOS would stir up all us old heads. I think what we're all really nostalgic for is the days of tinkering with computers. When things lacked polish, and people put real effort into making their system nice. I remember corrupting my family computer hard drive trying to get a Linux dual-boot setup. Good times!
JamesonNetworks 2 hours ago [-]
The true rite of passage for the child hacker I remember my dad and brother taking a floppy to copy a sys file to restore a win 3.1 install from the Sam’s display computer in the pre-internet days
peterashford 5 hours ago [-]
I think we were on the same track. I absolutely loved the Amiga and was about to jump on board BeOS when it went under. I never got to use BeOS as a daily driver (just ran their demo disk). How did you find it?
yason 3 hours ago [-]
From them internets after the x86 version got out, I think. Played enough with what I found around, and I ultimately bought (with real money) the BeOS 5.0 Personal Edition, made it dual-boot my Linux machine and knew that this is it! It felt like an Amiga but on soulless PC hardware instead! The exhilaration was unlimited! It booted fast, no old cruft, unorthodox designs, everything one-in-a-thousand a true harbinger customer loves!
Eventually I think the setup gradually bit rot with no updates and unsupported hardware, so I reluctantly had to go back to Linux. I remember Ubuntu and Gnome 2 started to look pretty nice (well, for an inferior desktop environment) in the early years of 2000.
(Unsurprisingly, years later Gnome came out with Gnome 3 and killed all the good stuff that Gnome 2 had accumulated. I can only wait and see how long Mate desktop survives.)
I still keep a Haiku VM around and boot it every now and then.
danans 1 hours ago [-]
I ran BeOS on both the dual PowerPC desktop and later on an x86 laptop. Thanks to its posix-ish environment, I was able to do all my upper division CS projects on it.
Others who had windows or macs had to "telnet" into a remote Unix workstation in an engineering lab to do the same.
prmoustache 4 hours ago [-]
I ran it in a dual boot with linux install but I ended up using Linux more despite liking beos because of the ecosystem. There were just more software available on Linux, especially lightweight tui tools.
hbbio 2 hours ago [-]
Don't get me started on the Psion 5mx...
Still have it, last time I checked it worked well.
makach 5 hours ago [-]
I had to read this message twice, gotcha
carlesfe 5 hours ago [-]
I ran BeOS as a daily driver for a few months in the early 2000s. I had a winmodem and Linux couldn't connect to the internet for me, but for some reason, BeOS had drivers, so I used it. It was faster and the desktop environment felt more polished than KDE/Gnome.
Of course, at that time, it was impossible to know which OS would win the wars, so BeOS became my favorite. However, Linux developed very quickly during those years, I got into college and started using UNIX there, winmodem drivers appeared, and that's what I ended up using.
But BeOS still holds a very dear place in my heart. It really was superior to anything else during that era.
dainiusse 5 hours ago [-]
+1. Even though it had limitations, it had this "clean polished feeling"
rebolek 10 hours ago [-]
If you like BeOS, take a look at Haiku https://www.haiku-os.org/ , it's very nice and very usable system based directly on BeOS.
pjmlp 9 hours ago [-]
And much better option, running the real deal, instead of some compatibility layer.
akho 5 hours ago [-]
I suspect Linux has better hardware support than Haiku, which is not exactly easy to run on laptop hardware (w/ wifi, sleep, &c)
SuperNinKenDo 2 hours ago [-]
I suspect it was a freak occurence, but I actually had incredible luck running Haiku on an old laptop back in the day. It was incredibly fast, and just about all the amenities you'd expect worked with no or minimal intervention.
pabs3 41 minutes ago [-]
In the last year sometime I ran the Haiku live image off USB on my only laptop (2011 X201t), it worked fairly well.
cachius 2 hours ago [-]
Even running from an HDD?
trinix912 52 minutes ago [-]
I recently tried the latest version (Beta 5?) on a 2005-ish PC with an even older HDD and it ran surprisingly fast off that. The only thing where it was somewhat slow was web browsing.
pjmlp 3 hours ago [-]
Yeah, a good opportunity to contribute upstream.
hrmtst93837 3 hours ago [-]
Maybe, but at some point you're duct-taping 90s driver hacks just to run Haiku on modern hardware unless you enjoy daily spelunking in kernel panics.
AlecSchueler 8 hours ago [-]
Presumably there's a lot more modern software written for Linux which you'd end up running through a compatibility layer from Haiku? The better option seems relative. I could be misremembering how Linux programmes are handled on Haiku though.
chrsw 4 hours ago [-]
VitruvianOS has the clothes of BeOS, which is nice and refreshing.
But Haiku has the soul.
pjmlp 8 hours ago [-]
Maybe the fallacy is not exploring what a given OS is great at?
We don't need to clone UNIX all over the place.
hnlmorg 6 hours ago [-]
How strictly do you mean “UNIX clone”? Because Linux isn’t strictly UNIX. But then at the other end of the scale, BeOS was also partially POSIX compliant and shipped with Bash plenty of UNIX CLI tools.
Perhaps it’s better to play it safe and just run DOS instead ;)
pjmlp 3 hours ago [-]
It certainly is, what it is not, is a derivative.
BeOS on its final commercial version certainly did not allow to compile UNIX applications, beyond the common surface that is part of ISO C and ISO C++ standard library.
c-c-c-c-c 8 hours ago [-]
But Vitruvian is running its own graphics stack so no X11 or wayland applications will run afaict.
hym_the_pawn 3 hours ago [-]
Not quite really.
Vitruvian runs virtually the same identical sw stack of Haiku and there's a haiku-wayland that works.
However on vitruvian the app_server could provide real Gbm buffers, so that would give us pretty much native rendering.
We're still working on it but you'd have the advantages of a BeOS-like gui and the power of linux!
reverius42 6 hours ago [-]
So what's the point of this -- it's essentially a different Haiku?
galangalalgol 4 hours ago [-]
I think itbis the reverse, it is haiku with a linux kernel so it works with more hardware.
5 hours ago [-]
anthk 7 hours ago [-]
With xlibe they should.
shevy-java 7 hours ago [-]
And things such as ruby don't work on it. Well, what shall
I say? The "best" ideas get beaten when in practically already
works very well - aka Linux. People need to compare to Linux
and if there are failure points, they need to fix it. Haiku
keeps on failing at core considerations. If you look at guides,
they recommend to "run in qemu". Well, that is a fever dream.
They need to focus on real hardware. And they need to support
programming languages just as Linux does. And modern hardware
too. Would be great if Haiku could shape up but the development
is way too slow. I've been looking at it for many years - they
are simply unable to leave the dream era. ReactOS is even worse
in this regard. At some point those projects gave up on the real
world. I think qemu, while great, kind of made this problem
worse, since people no longer focus on real hardware; the mantra
is "if it works in a virtual EM, it is perfect". Until one notices
that it doesn't work quite as well on real hardware. Case in point
how ruby does not work on Haiku. Ruby works well on BSD (for the most
part), linux (no surprise) and also windows (a bit annoying, but it
does work there too and surprisingly well, for about 99% of the use
cases, though it is annoyingly slower in startup time compared to
linux).
chuckadams 2 hours ago [-]
Huh, PHP works on Haiku, and there aren't even that many #ifdefs for it in the source. If a language can be ported to Windows, Haiku should be a no-brainer. Seems more a matter of having someone interested in maintaining the port, and I think it ultimately just points to the size of Haiku's userbase being a rounding error.
59nadir 3 hours ago [-]
> I've been looking at it for many years - they are simply unable to leave the dream era.
Sit down and do the work needed to get Ruby running properly on Haiku instead of sitting here complaining and basically admitting that you're just being a noisy spectator... On HackerNews, no less.
rebolek 6 hours ago [-]
Getting Rebol running on Haiku was fairly easy task, so I guess it shouldn't be that hard for Ruby too, if someone's willing to do the work.
pjmlp 7 hours ago [-]
People aren't really running servers on Haiku, which is basically the only relevance to use Ruby in 2026, Rails powered web applications.
Then again, there is a golden opportunity to become a Ruby contributor, road to fame on Ruby contribution list.
cpuguy83 2 hours ago [-]
Homebrew would like a word.
pjmlp 8 minutes ago [-]
Mostly relevant for folks on macOS, and I skip on it when using Mac anyway rather using UNIX and SDK tools in the box, so kind of debatable.
timw4mail 55 minutes ago [-]
Homebrew wouldn't support Haiku anyway.
10729287 7 hours ago [-]
I've been a fan of Beos philosophy since the Personal Edition but never had the occasion to run it on steel as I was too poor to have two machines back in the days, and now I miss login/password prompt at boot on Haiku. But i'm following it closely and I hope i'll be able to install it on my X220 for a web/mail machine !
hnlmorg 6 hours ago [-]
You didn’t need two machines to run BeOS. I ran very smoothly on a Windows PC via dual booting.
BeOS 5 could even be installed on a Windows FAT32 partition alongside Windows (it created a 50MB virtual disk).
At one point in time I had Windows 95, Windows 2000, Linux (possibly Slackware) and BeOS 5 all running on the same single PC.
10729287 1 hours ago [-]
I was probably younger than you, and on the family computer. Couldn't make what I want and mess with booting back then ! I remember trying the PE edition through windows but couldn't install it.
hym_the_pawn 4 hours ago [-]
Vitruvian can potentially have everything Haiku has (it's the same identical stack BTW) but with the power of linux.
It's cool if people could start to appreciate both visions.
25 years ago, I configured GNOME to run a BeOS-like tabbed window manager. On a sun workstation.
But that's not what this is. Or not only:
Nexus Kernel Bridge
Nexus is Vitruvian's custom Linux kernel subsystem that brings BeOS-style node monitoring, device tracking, and messaging to Linux — making it possible to run Haiku applications on a standard Linux kernel.
It claims to run apps from Haiku, the current open-source implementation of a modern BeOS.
zozbot234 5 hours ago [-]
Looks like this is a thin translation layer for BeOS/Haiku syscalls. I wonder why they aren't relying on Syscall User Dispatch https://docs.kernel.org/6.19/admin-guide/syscall-user-dispat... which would enable them to put this compatibility layer in user space. It's already being used by recent Wine versions.
hym_the_pawn 4 hours ago [-]
It's not really a translation layer, nexus implements the same BeOS/Haiku IPC in kernel but using linux kernel primitives.
It's not as much as a translation layer than any other IPC in the linux system, really BeOS/Haiku apps are first class citizens.
5 hours ago [-]
donatj 9 hours ago [-]
The important question becomes can you stack the window decoration "tabs" of different apps into a single stack of tabs like in BeOS?
I used to run fluxbox in the early 2000s. I greatly miss tabbing any windows like that.
malicka 48 minutes ago [-]
You can run fluxbox today! I still do, I can’t go without window tabs. :^)
gedy 4 hours ago [-]
I believe the Cosmic Desktop from Pop OS has that again
guerrilla 6 hours ago [-]
There's no equivalent on Wayland?
BirAdam 3 hours ago [-]
Sway.
nunodonato 6 hours ago [-]
me too! fluxbox and gkrellm for some kick ass desktop "widgets" monitoring the computer :D
Zardoz84 4 hours ago [-]
KDE had it. And I missed it a lot.
samtheDamned 2 hours ago [-]
I tried to install a quick VM to answer this exact question but I had some difficult getting it running in Gnome Boxes.
guerrilla 6 hours ago [-]
This is what we needed in our OSes instead of Firefox tabs.
Schlagbohrer 4 hours ago [-]
How is it that different?
yesbut 4 hours ago [-]
basically every app is a tab. this is how I run i3wm. full screen tabbed layout. smaller modal windows still appear in their normal smaller windows in front of the current full screen app.
numerio 6 hours ago [-]
Yes the UX is virtually the same
WD-42 9 hours ago [-]
UI elements that have depth look so mouth-wateringly good now. So over the minimalism and bouncing back hard.
716dpl 43 minutes ago [-]
I find it soothing. There is ornamentation in its design, but it's precise and minimal, but also friendly. The icons, in particular, look so good.
pndy 7 hours ago [-]
It fitted right these times when everything had that pseudo-3D gray outlook but yet was unique with these small yellow title bars (which you could move), diagonal icons and taskbar that could be placed in both corners and edges of the screen. Now compare that last thing to what MS did to Windows 11 taskbar, and only in last days announced it'll gladly restore previous behavior.
Haiku retained all of this and bring something new like combining various windows into single tabbed one - not sure if any other system has such feature. Or... toolbar in file manager - which is something I really missed back then in BeOS.
Back then BeOS was much more stable and faster than my daily Win98SE, even working in that image file on FAT32 partition.
Kinda makes you wonder, how things would go if Apple would pick BeOS as their OS instead of Jobs' NeXT. Would it still looks same or it would go thru all stages we've seen - with glass, transparency and then flatness and darkpatterns producing minimalism.
diskzero 41 minutes ago [-]
As a former Be employee who ended up at Apple by way of Eazel, there are two ways to answering your question about the UI direction; 1. If Apple did not acquire Be, Apple most likely would not be in business or would be a much different company. 2. Assuming Apple did survive, Steve Jobs used the industrial design language of Jony Ive for the look of Aqua. Bas Ording was the primary designer of this and was directed by Steve with daily updates. The further evolutions of brushed metal, skeumorphism, etc. were all directly driven by how Steve wanted things to look with minimal input from others. The current bland minimalist UX disaster (IMHO) would probably not have happened, because for all of his faults, Steve had very good attention to detail and was in general a good proxy for the user.
kannanvijayan 3 hours ago [-]
I remember being very disappointed when Apple went with the NeXT tech instead of the Be tech. I was in undergrad when that happened.
In retrospect though, the company wasn't making a technology decision. They were making a decision between Jobs and Gassee. Jobs came with NeXT and Gassee came with Be.
I don't think the technology mattered that much in the large scale of things. Jobs brought with him a strategy for moving personal computing from a technical market category to a fashion market category - either to make technology fashionable or to make fashion technical (however you want to look at it). It's a strategy that started with candy-coloured iMacs and ended with iPhones.
Gassee brought a really cool OS.
Apple made the right choice.
diskzero 31 minutes ago [-]
In retrospect though, the company wasn't making a technology decision. They were making a decision between Jobs and Gassee. Jobs came with NeXT and Gassee came with Be.
I don't think the technology mattered that much in the large scale of things.
Yes and no. The core of the purchase decision was really based on the technology. Ellen Hancock (Apple's CTO at the time) actually did a decent analysis of BeOs and NeXTStep. She was actually against some aspects of the purchase, and was not in favor of Be. She was also not in favor of the NeXT kernel. It is painful to say as a Be employee at the time, but Be internals were fragile, some technologies were very shallow, the kernel was brittle and under constant churn and we had big problems with our decision to have a C++ API. Gil Amelio liked Steve and Steve did a good job selling both a vision and the NeXT technology. BeOs was a really cool demo that was getting pulled into the direction of a real OS but had a long, long way to go. There actually was a possibility that Apple could have also gotten the Be code, but the board didn't go for it. As it turned out, most of the primary BeOs developers ended up at Apple via Eazel. The ones that didn't ended up at Google via Danger Research/Android.
chuckadams 2 hours ago [-]
I believe the saying goes that NeXT acquired Apple for -$427 million.
InsideOutSanta 3 hours ago [-]
Late 90s visual design for operating systems - in particular Mac OS 8 and BeOS - is peak OS design. Aesthetically pleasing and a very clear, highly readable visual language based on well-researched human interface guidelines.
It was uphill all the way before that point, and downhill ever since.
thisislife2 10 hours ago [-]
This is interesting - a Linux distro that really differentiates itself technically, instead of just having a different GUI / desktop environment.
Yaggo 4 hours ago [-]
Yeah, first I thought this is just a BeOS-inspired GUI theme, but there is more to it:
Nexus is Vitruvian's custom Linux kernel subsystem that brings BeOS-style
node monitoring, device tracking, and messaging to Linux — making it
possible to run Haiku applications on a standard Linux kernel.
nathell 50 minutes ago [-]
I almost overlooked this, and then when I didn’t, I almost dismissed this as Yet Another Linux Distro with a custom skin. But no, there’s novelty and exploration in here. There’s attempt to venture off the local maximum. This is a breath of fresh air.
vibbix 48 minutes ago [-]
Pleasant surprise to hear about this. I've had a fascination with BeOS & Haiku for decades. I am now actually developing a custom website layout themed after BeOS (good excuse to learn Figma!)
nico 9 hours ago [-]
BeOS was such an amazing experience back in the day. It really felt magical. Too bad it got shutdown. I wonder what the evolution of it would be like today
silisili 9 hours ago [-]
My first memory of BeOS was that it could play media independently. You could play a video in one window, and an MP3 or another video in another, and they'd both play audio at the same time.
I don't know exactly why, but child me thought that was so interesting, since every other OS at the time seemed unable to.
I love Haiku but I feel it's quite different than where BeOS would be today had BeOS continued to exist. In that alternative world there might have been considerably more influence from BeOS going into the rest of the industry much sooner, and that effect could have snowballed.
pjmlp 8 hours ago [-]
For me it felt like it was going to be my next Amiga, in kind of experience, something that GNU/Linux never did it to me, where CLI reigns and multimedia was always looked down upon, Windows and Mac OS weren't quite there as well.
Another cool one that was around was QNX.
setopt 8 hours ago [-]
If I recall directly, Apple was between buying BeOS and NeXT. Would be interesting what would have happened if they went the Be route instead of the Unix route. (But given that MacOS and BeOS were both fringe at the time, perhaps they would just have gone bankrupt…)
ab5tract 8 hours ago [-]
Considering that Steve Jobs came with NeXT, the general consensus has been that their recovery would not have been nearly as significant.
The real what-if for me is pondering what might have been had HP and other vendors not caved to the Wintel cartel in abandoning their plans to include BeOS as a preinstalled OEM option. Microsoft was sued by Be in civil court and Be won their case, but it was too little too late.
BirAdam 3 hours ago [-]
Jobs worked on NeXT and Jean-Louis Gassée was working on Be. Gassée had brought the world the Macintosh Portable and the IIfx, and he started the Newton project which had the effect of keep ARM alive.
When Gassée left Apple, he took many of Apple's best with him. If we want to know what Apple would have looked like under Gassée, I think it's easier to look at how many products he killed. Much of Apple's leadership was trying to force budget computers like the PC industry was building. Gassée would have none of it. He was focused on exceptionally good hardware married to exceptionally good software, knew the handheld devices would be vital in the future, but he didn't like boring things. I imagine that Apple built around Be would have delivered many of the same things, but wouldn't have become just plain brushed aluminum everywhere.
The curious part would have been the OS. BeOS and NeXT are wildly different.
panick21_ 8 hours ago [-]
I think at the time everybody agree that BeOS would need a whole lot more work put into it compared to NeXT. That said it still took a huge amount of work to evolve NeXT to OSX.
So I can well imagine Apple fucking this up and getting aquired.
ErroneousBosh 8 hours ago [-]
You can pretty much just use Haiku as a daily driver these days, if your demands aren't too great. It runs really well on older hardware too.
And of course you can just spin it up in a VM if you only want to play a bit.
innocentoldguy 8 hours ago [-]
I just found my BeOS 5 and BeProductive CDs from the late 90s. I wish I had something to run them on.
mlhpdx 3 hours ago [-]
What would they run on these days? I mean other than my old Gateway 2000 dual Pentium Pro with 32MB of RAM and dual booting BeOS and NT4?
vanderZwan 5 hours ago [-]
Sort-of unrelated (but very on-brand for people into BeOS I think), it's so satisfying when a webpage is so free of bloat that navigation and latency to clicking on things in general feels instant.
_spduchamp 2 hours ago [-]
BeOS had the BEST icons.
2 hours ago [-]
aaronbrethorst 10 hours ago [-]
Vitruvian asks a different question: what would I actually want to do with my computer that I currently can’t?
Only be able to drag a window around the screen from the top left corner
danwills 8 hours ago [-]
On many Linux desktop environments it is the default - or can be configured: To hold the Windows Key ('meta') and left-mouse-drag a window around from _anywhere inside the window_! No need to get the mouse into the 'title bar'!
Additionally, meta+middle-mouse-drag allows one to resize a window from anywhere in the whole window!! (it chooses the closest corner when the drag starts) and this, being able to resize a window without needing to put the mouse in a usually-very-thin window border, is extremely liberating in my opinion! To the point where I really miss it on sub-windows where the app is handling resizing/etc itself!
There's a Windows app I used to use that supports the same kind of thing for Windows (different key I think), no idea if there's one for Mac I'm afraid - or whether it can be configured to work that way, but there probably is one so it would be worth investigating if this sounds useful to you I'd say!
bandie91 4 hours ago [-]
yes, Alt+drag (it's always meta, not meta4, by default on systems i use) has been and still is a killer feature to me. on desktops which does not support it, like windows, i feel like my hands were tied.
ianlevesque 10 hours ago [-]
To be fair that's one more corner than Tahoe.
aaronbrethorst 10 hours ago [-]
Touché, and such a good reminder why everyone should wait for macOS 27.
weli 2 hours ago [-]
Is this using haiku as a kernel or is it a complete re-implementation of BeOs/Haiku API's? I can't tell by their website or github.
rcarmo 8 hours ago [-]
I hope it’s not just the look. The ability to group tabs from various apps into a single window was the best UX feature it had, and I still miss it sometimes.
numerio 6 hours ago [-]
it's the real app_server running :) so you have everything you'd expect
prmoustache 4 hours ago [-]
Anyone remember BlueEyedOS? It had exactly the main goal, building a beos compatible OS on top of the Linux kernel.
hencq 3 minutes ago [-]
Yes! I was racking my brain trying to remember what it was called. Back in the early 2000s I ran BeOS on my desktop and absolutely loved it. Then when they went under, I followed the effort to come up with an open source version with guest interest. There was one effort that wanted to build everything from scratch. That's what was later renamed into Haiku (I think initially openBeOS maybe?). There was also BlueEyedOS who thought you could get there faster by building on Linux and X11.
I think Haiku got more traction because at the time people felt that it should run BeOS software without recompiling. I have long wondered what would have happened if BlueEyedOS would have gotten most of the effort.
aryonoco 3 hours ago [-]
Little known fact, a small piece of BeOS survives to this day and is an integral part of Android
BeOS came up with “Binder” for doing inter process communication. Just before Be Inc. was acquired by Palm, some Be engineers somehow convinced management to release Binder as open source, which came to be known as OpenBinder.
After the Palm acquisition many Be engineers moved to a startup called Android Inc, and adopted OpenBinder for IPC. And the rest as they say, is history.
pjmlp 4 minutes ago [-]
Another thing that survives is that they wrote Java as if writing C++ with m_ prefixes, and several other Cisms, which prevail to today.
It’s Linux, with all of the support that provides. Not a knock on Haiku, but if I can have a BeOS window manager and Tracker, while running modern Linux binaries natively, I’d be a happy.
Gabrys1 8 hours ago [-]
For my daily machine, I need Docker, terminal, Firefox (for private browsing), Chrome (for work), VS Code and/or JetBains IDE. If this can feel a bit like I remember BeOs felt, that'd be awesome
pjmlp 8 hours ago [-]
You mean Electron apps.
rubymamis 3 hours ago [-]
Can someone list what are some cool/novel BeOS features that other OSes didn’t have at the time and maybe still don’t have?
ofrzeta 10 hours ago [-]
"Real-time patched Linux kernel for low-latency desktop use" - does this really make sense? I think there have been various efforts like this over the decades but as far as I remember none of them really made a huge difference for the end user.
worthless-trash 8 hours ago [-]
IIRC the realtime patchset that RHEL maintained in its own branch/tree was upstreamed last year.
I don't think it makes sense for desktop applications, it may make sense if sound latency is a priority but even then stock kernel delivered lower latency in many cases.
numerio 5 hours ago [-]
I won't say you're wrong because you aren't, in fact the system works very well also with non-rt kernels. But the graphical stack is not really designed like the average linux stack, the BeOS is somewhat hungry in terms of timing and I believe our implementation can take advantage of a RT kernel. But if it'd proven unnecessary I'd be 100% for changing it back, it's just a package in our image creation code after all, we don't strictly depend on it.
hrmtst93837 6 hours ago [-]
[dead]
clayhacks 8 hours ago [-]
Ok maybe I’m too young, but what is BeOS? Everyone here is linking other alternatives, but no one’s linked to the original BeOS. Or is it gone now?
lobf 8 hours ago [-]
I don't understand this type of helplessness when you're already competent enough to use HN...
Thank you everyone for commenting! We are going to pubblish small articles on the website to clarify some of the common questions that are popping around. We will also do our best to improve our wording and marketing, thanks everyone for the suggestions and stay tuned!
jazzyjackson 9 hours ago [-]
I’ll try this out with my eink display, interface might look good in grayscale. So far my favorite desktop for this is the Chicago95 theme for xfce
dddw 8 hours ago [-]
Do share a screenshot if you do. What refreshrate do you have on that display?
flippyhead 2 hours ago [-]
Even if the cheaps are weak... is the code strong?
Ah yes! It is human at the center. Now things are starting to make sense.
unmole 10 hours ago [-]
I don't see any actual context, just vacuous slop.
s1mn 6 hours ago [-]
I was never cool enough to run BeOS but I coveted it. It looked so cool and futuristic compared with Windows.
I'm not cool enough to run VitruvianOS either, but i'm glad it exists.
9 hours ago [-]
add2 6 hours ago [-]
How about making Haiku frameworks OS independent?
Findecanor 4 hours ago [-]
There is a blog entry [0] on the web site mentioning that they needed a Linux kernel module for some missing filesystem pieces, and also configure the kernel to be realtime.
I wonder what they will do to support BeOS' MediaKit. It has packet streams with realtime delivery.
We have the same IPC that BeOS/Haiku has so it'd run natively, but actually Vitruvian will provide a new modern media framework that is compatible with the old media kit through an external compat library.
jonhohle 9 hours ago [-]
Is this a new window manager and tracker or something skinned for this use case? Wayland, X11? There’s a screenshots section but the details are sparse.
Findecanor 4 hours ago [-]
It is a native windowing system, probably a port from Haiku.
There exists at least one rootless X11 server for BeOS/Haiku that would run on top, that shouldn't be too difficult to port (knock on wood ...)
riffraff 9 hours ago [-]
It runs haiku apps through a compatibility layer
numerio 5 hours ago [-]
it's a little bit more of a compatible layer, it's just a native implementation really. You wouldn't call android a "compatibility layer" right? Kind of a similar idea here.
asadm 10 hours ago [-]
is there a debian distro that is close to win98. Sorta like ReactOS but can be daily-driven.
Because they're enthusiastic engineers. Not marketing people.
lnxg33k1 7 hours ago [-]
> It’s very easy to use. It features an intuitive desktop
> and adopts KISS principles. Anyone can rapidly feel at
>home and use V\OS. User experience, workflow and comfort
> is key.
What is more intuitive than a button to close a window without a X, in order to make people from every other OSes feel at home
https://v-os.dev/img/photogrid.png
-- When words have no meaning
numerio 5 hours ago [-]
I don't understand the ragebait here. First thing, it's the BeOS GUI that is like that. Secondarily, seems to me also MacOS X lacks a X button? Or did they change it? Third, we can discuss about that, it's trivial to change.
Cheers
leke 10 hours ago [-]
So this is a lighter weight alternative to other Linux desktops?
tadfisher 9 hours ago [-]
Well, it can't run X or Wayland apps, so I wouldn't call it an alternative to those. An alternative to Haiku maybe.
Gabrys1 8 hours ago [-]
why no X11?
ErroneousBosh 8 hours ago [-]
Because everyone's going for Wayland, even though you still need XWayland to do anything useful on it because Wayland is comically incomplete.
Gabrys1 4 hours ago [-]
well, I mean, why can't this ship with an X server? Or maybe it does and then I'm not sure why it is said that only Haiku apps are supported
numerio 3 hours ago [-]
It's not that it can't, if you can do something it doesn't mean you should. If we used X it'd be another linux distro isn't it? Part of the fun is to make your own UI feel.
shevy-java 7 hours ago [-]
It's been a pain to try to get ruby to work on Haiku,
so I expect that this will be like linux - but worse,
in that barely anything works. I like the design choices
made by BeOS, but we have 2026 now. Linux kind of showed
that practical considerations beat theoretical superiority
(except for the desktop segment, where Linux keeps on
failing hard; see GTK5 not supporting xorg, it is now the
all corporate-dictated wayland era).
numerio 20 minutes ago [-]
[dead]
Rendered at 15:18:49 GMT+0000 (Coordinated Universal Time) with Vercel.
I bought BeOS in the late 90's and enjoyed it immensely like a breath of fresh air in a sewage pipe. BeOS died.
With my track record I really, really should've bought Windows. Twice, to make sure.
https://mitsloan.mit.edu/ideas-made-to-matter/working-defini...
Eventually I think the setup gradually bit rot with no updates and unsupported hardware, so I reluctantly had to go back to Linux. I remember Ubuntu and Gnome 2 started to look pretty nice (well, for an inferior desktop environment) in the early years of 2000.
(Unsurprisingly, years later Gnome came out with Gnome 3 and killed all the good stuff that Gnome 2 had accumulated. I can only wait and see how long Mate desktop survives.)
I still keep a Haiku VM around and boot it every now and then.
Others who had windows or macs had to "telnet" into a remote Unix workstation in an engineering lab to do the same.
Still have it, last time I checked it worked well.
Of course, at that time, it was impossible to know which OS would win the wars, so BeOS became my favorite. However, Linux developed very quickly during those years, I got into college and started using UNIX there, winmodem drivers appeared, and that's what I ended up using.
But BeOS still holds a very dear place in my heart. It really was superior to anything else during that era.
But Haiku has the soul.
We don't need to clone UNIX all over the place.
Perhaps it’s better to play it safe and just run DOS instead ;)
BeOS on its final commercial version certainly did not allow to compile UNIX applications, beyond the common surface that is part of ISO C and ISO C++ standard library.
Sit down and do the work needed to get Ruby running properly on Haiku instead of sitting here complaining and basically admitting that you're just being a noisy spectator... On HackerNews, no less.
Then again, there is a golden opportunity to become a Ruby contributor, road to fame on Ruby contribution list.
BeOS 5 could even be installed on a Windows FAT32 partition alongside Windows (it created a 50MB virtual disk).
At one point in time I had Windows 95, Windows 2000, Linux (possibly Slackware) and BeOS 5 all running on the same single PC.
But that's not what this is. Or not only:
Nexus Kernel Bridge
Nexus is Vitruvian's custom Linux kernel subsystem that brings BeOS-style node monitoring, device tracking, and messaging to Linux — making it possible to run Haiku applications on a standard Linux kernel.
It claims to run apps from Haiku, the current open-source implementation of a modern BeOS.
Demonstrated here (animated):
https://www.haiku-os.org/docs/userguide/en/images/gui-images...
Haiku retained all of this and bring something new like combining various windows into single tabbed one - not sure if any other system has such feature. Or... toolbar in file manager - which is something I really missed back then in BeOS.
Back then BeOS was much more stable and faster than my daily Win98SE, even working in that image file on FAT32 partition.
Kinda makes you wonder, how things would go if Apple would pick BeOS as their OS instead of Jobs' NeXT. Would it still looks same or it would go thru all stages we've seen - with glass, transparency and then flatness and darkpatterns producing minimalism.
In retrospect though, the company wasn't making a technology decision. They were making a decision between Jobs and Gassee. Jobs came with NeXT and Gassee came with Be.
I don't think the technology mattered that much in the large scale of things. Jobs brought with him a strategy for moving personal computing from a technical market category to a fashion market category - either to make technology fashionable or to make fashion technical (however you want to look at it). It's a strategy that started with candy-coloured iMacs and ended with iPhones.
Gassee brought a really cool OS.
Apple made the right choice.
Yes and no. The core of the purchase decision was really based on the technology. Ellen Hancock (Apple's CTO at the time) actually did a decent analysis of BeOs and NeXTStep. She was actually against some aspects of the purchase, and was not in favor of Be. She was also not in favor of the NeXT kernel. It is painful to say as a Be employee at the time, but Be internals were fragile, some technologies were very shallow, the kernel was brittle and under constant churn and we had big problems with our decision to have a C++ API. Gil Amelio liked Steve and Steve did a good job selling both a vision and the NeXT technology. BeOs was a really cool demo that was getting pulled into the direction of a real OS but had a long, long way to go. There actually was a possibility that Apple could have also gotten the Be code, but the board didn't go for it. As it turned out, most of the primary BeOs developers ended up at Apple via Eazel. The ones that didn't ended up at Google via Danger Research/Android.
It was uphill all the way before that point, and downhill ever since.
I don't know exactly why, but child me thought that was so interesting, since every other OS at the time seemed unable to.
Another cool one that was around was QNX.
The real what-if for me is pondering what might have been had HP and other vendors not caved to the Wintel cartel in abandoning their plans to include BeOS as a preinstalled OEM option. Microsoft was sued by Be in civil court and Be won their case, but it was too little too late.
When Gassée left Apple, he took many of Apple's best with him. If we want to know what Apple would have looked like under Gassée, I think it's easier to look at how many products he killed. Much of Apple's leadership was trying to force budget computers like the PC industry was building. Gassée would have none of it. He was focused on exceptionally good hardware married to exceptionally good software, knew the handheld devices would be vital in the future, but he didn't like boring things. I imagine that Apple built around Be would have delivered many of the same things, but wouldn't have become just plain brushed aluminum everywhere.
The curious part would have been the OS. BeOS and NeXT are wildly different.
So I can well imagine Apple fucking this up and getting aquired.
And of course you can just spin it up in a VM if you only want to play a bit.
Only be able to drag a window around the screen from the top left corner
Additionally, meta+middle-mouse-drag allows one to resize a window from anywhere in the whole window!! (it chooses the closest corner when the drag starts) and this, being able to resize a window without needing to put the mouse in a usually-very-thin window border, is extremely liberating in my opinion! To the point where I really miss it on sub-windows where the app is handling resizing/etc itself!
There's a Windows app I used to use that supports the same kind of thing for Windows (different key I think), no idea if there's one for Mac I'm afraid - or whether it can be configured to work that way, but there probably is one so it would be worth investigating if this sounds useful to you I'd say!
I think Haiku got more traction because at the time people felt that it should run BeOS software without recompiling. I have long wondered what would have happened if BlueEyedOS would have gotten most of the effort.
BeOS came up with “Binder” for doing inter process communication. Just before Be Inc. was acquired by Palm, some Be engineers somehow convinced management to release Binder as open source, which came to be known as OpenBinder.
After the Palm acquisition many Be engineers moved to a startup called Android Inc, and adopted OpenBinder for IPC. And the rest as they say, is history.
https://www.desktoponfire.com/interview/846/an-interview-wit...
I don't think it makes sense for desktop applications, it may make sense if sound latency is a priority but even then stock kernel delivered lower latency in many cases.
https://en.wikipedia.org/wiki/BeOS
https://v-os.dev/news/vitruvian-0.3.0-available/
I'm not cool enough to run VitruvianOS either, but i'm glad it exists.
I wonder what they will do to support BeOS' MediaKit. It has packet streams with realtime delivery.
[0] https://v-os.dev/blog/2026/02/10/haiku-runtime-on-linux/
There exists at least one rootless X11 server for BeOS/Haiku that would run on top, that shouldn't be too difficult to port (knock on wood ...)
https://github.com/grassmunk/Chicago95
"VitruvianOS is an alternative Linux desktop with a singular philosophy: the human at the center."
https://v-os.dev/news/vitruvian-0.3.0-available/
> and adopts KISS principles. Anyone can rapidly feel at
>home and use V\OS. User experience, workflow and comfort
> is key.
What is more intuitive than a button to close a window without a X, in order to make people from every other OSes feel at home https://v-os.dev/img/photogrid.png
-- When words have no meaning
Cheers