3 ms·
having worked with ruby & rails both for about 7 years, i've run into my fair share of gem hairballs. in general, i've had _more_ problems on osx than on linux
by mml 14y ago
having worked with ruby & rails both for about 7 years, i've run into my fair share of gem hairballs.
in general, i've had _more_ problems on osx than on linux, mostly due to various ARCH flags required by c extensions.
that being said, the "system rubies" on every linux distro i've used are generally infinitely horrible, and this is likely the case for the poster. system packaged gems are also insanely gross as well.
one of ruby's saving graces is that at least it's not used by the base system for initialization, which has bit me more than once installing a python that conflicted with the system python (though that was many years ago, things may have improved).
rvm has its own issues (and seems to be getting more complex with every rev), but in general, makes for clean living. bundler is nice too.
- josephmosby 14y agoI had not really thought about why Python development generally expected a virtualenv until now. If you haven't been in the Python world at all, virtualenv essentially sets up a miniature development environment within your working folder. System Python might be version 2.7.3, but inside my virtual environment I can run Python 3.0. It's a nice little hack around the problem of multiple Python versions... doesn't solve the root cause, but at least you can stitch it up with one step.