[AlecSchueler]

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]

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

But Haiku has the soul.

[pjmlp]

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]

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]

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.

[numerio]

maybe in early BeOS versions but, BeOS R5 especially with the BONE updates had a fairly decent POSIX compatibility for the time. If you do "ls /" you can see immediatly BeOS has some BSD reminiscence, but certainly it isn't a UNIX OS as in itself.

[c-c-c-c-c]

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

[hym_the_pawn]

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]

So what's the point of this -- it's essentially a different Haiku?

[galangalalgol]

I think itbis the reverse, it is haiku with a linux kernel so it works with more hardware.

[anthk]

With xlibe they should.

[smallstepforman]

In Haiku windowing system, each app window gets its own thread so dialog boxes run in a different thread to the main window and a different thread to the core app. In Linux, all windows share the same message loop thread. A simple port reveals threading issues in Haiku which dont exist on Linux.

To work around this, all window messages in ported apps are marshalled to execute sequentially. Small additional overhead, and the system doesnt spread available threads, so noticably slower.

Compare a native Haiku app with a ported app, one is smooth as ice while the other isnt. Users notice it. This is on many core systems.

[jcgl]

> In Linux, all windows share the same message loop thread.

I'm no expert, but aren't you just talking about Xorg here? As far as my limited knowledge goes, there's nothing inherent in the Wayland protocol that would imply this.