Live data from Hacker News

VitruvianOS – Desktop Linux Inspired by the BeOS

v-os.dev

101–110 of 234 posts

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#101
post #20

Earlier quoted context omitted.

And much better option, running the real deal, instead of some compatibility layer.

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.

VitruvianOS has the clothes of BeOS, which is nice and refreshing.

But Haiku has the soul.

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#102

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

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 win…

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.

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#104
post #77
post #20

Earlier quoted context omitted.

And much better option, running the real deal, instead of some compatibility layer.

I suspect Linux has better hardware support than Haiku, which is not exactly easy to run on laptop hardware (w/ wifi, sleep, &c)

Yeah, a good opportunity to contribute upstream.

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#105
post #90

Earlier quoted context omitted.

Because everyone's going for Wayland, even though you still need XWayland to do anything useful on it because Wayland is comically incomplete.

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

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.

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#106
post #65
post #34

Earlier quoted context omitted.

Maybe the fallacy is not exploring what a given OS is great at? We don't need to clone UNIX all over the place.

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 ;)

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.

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#107

Earlier quoted context omitted.

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.

But Vitruvian is running its own graphics stack so no X11 or wayland applications will run afaict.

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!

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#108
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.

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#109
post #54

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.

I think I did this with phones. WebOS, BB10, Windows Phone 7 & 8. All dead lol.

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.

Re: VitruvianOS – Desktop Linux Inspired by the BeOS

#110
post #64

How about making Haiku frameworks OS independent?

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. [0] https://v-os.dev/blog/2026/02/10/haiku-runtime-on-linux/

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.
Post reply on HN