So true. I had an old Dell Latitude D620, 3GB/500GB, 1.66ghz Intel Core Duo Processor and it was sound that tripped me up. Haiku was lightning fast on this machine.
I think that eventually I might've gotten sound to work but... this was many years ago and the laptop was mostly for testing light-weight distros on modest hardware.
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.
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.
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 ;)
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.
What doesn't work about it? We have Ruby in the software repositories, and Ruby is required to build WebKit (and we build WebKit on Haiku), so clearly it works for that much at least. I don't see any open tickets at HaikuPorts about bugs in the port, either.
Then again, there is a golden opportunity to become a Ruby contributor, road to fame on Ruby contribution list.
