Re:Installing Rails on a Mac Shouldn't Be As Hard As It Is
by pyre on Tuesday July 10, 2012 @01:04PM
(#4224838)
The php interpreter isn't used by system processes. I'm not sure how essential the stock Ruby interpreter, but I know that on Linux the system Perl & Python interpreters are used by system processes and upgrading them could potentially break things.
Re:Installing Rails on a Mac Shouldn't Be As Hard As It Is
by jasomill on Wednesday July 11, 2012 @01:01AM
(#4227802)
OS X Server uses both PHP and Ruby. From my Lion Server:
jtm@vertex ~ $ find /usr/share -iname *.php | wc -l
165
jtm@vertex ~ $ find /usr/share -iname *.rb | wc -l
5855
Even if you don't use OS X Server, Ruby.framework has been part of the API since Leopard [1], so applications can (and do) depend on it.[1] https://developer.apple.com/library/mac/#documentation/MacOS...
Re:Installing Rails on a Mac Shouldn't Be As Hard As It Is
by apl on Tuesday July 10, 2012 @01:19PM
(#4224955)
> [...] accidental, inessential, complexity [...]
Sure, but when that complexity is so utterly minuscule, what's the point in shielding users from it? Especially when you could argue that it benefits the user who will, at the very least, roughly know what's powering his application?
I don't think it inherently require anything like that for _installing_.
There is essential complexity (e.g the complexity of developing a RoR app), and accidental, inessential, complexity.
Installation not being a one click / command process is inessential complexity. It's just that the people involved (and the people NOT involved) have failed to make it any better.
For example, one can install Apache/PHP/MySQL on a Mac in a single package in 1 minute (via MAMP).