Well a quick read to the point where he talks about doing Rails development makes it hard for Haiku in the door since installing Ruby Gems, etc… is not supported due to the apparent lockdown on the System folder (for good reason the Haiku core developers can better explain). This issue also affects Python packages, etc…
I am hoping by the time Haiku hits the final R1 release that these sort of issues get ironed out. I think it’s in the best interest of the Haiku platform to become highly developer friendly as that could be a boon for end-user adoption.
Ruby gems can be installed in the user directory, but it needs a command line switch to do so. Python was patched to install packages in a writable place, so that works out of the box. Perl was patched in a similar way and works, too.
If you still have problems, be sure to report them to haikuports if you want to see things fixed.
Adjust site-packages to be writable (by moving it into non-packaged hierarchy).
Add vendor-packages directory, where packaged python modules shall be installed.
Add support for automatically installing modules into vendor directory when HAIKU_USE_VENDOR_DIRECTORIES is set.
I think Ruby has support for a similar setup, it just needs the various default paths to be adjusted to do the right thing (install in non-pakaged, unless HAIKU_USE_VENDOR_DIRECTORIES is set). We use HAIKU_USE_VENDOR_DIRECTORIES when building python packages in haikuports so they install at the right place to put them in an hpkg file.