upvote
What does not work? You can install Ruby version 3.2.9 (2025-07-24) with a point-and-click package manager HaikuDepot and it works perfectly fine.
reply
> 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.

reply
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.
reply
> And things such as ruby don't work on it.

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.

reply
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.
reply
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.

reply
Maybe 5% of what I use Ruby for is on the server. I'd suggest those of us who use Ruby client side are likely to outnumber Haiku users by magnitude or two.
reply
Homebrew would like a word.
reply
Homebrew wouldn't support Haiku anyway.
reply
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.
reply
Debatable because you don't use it?
reply