Re:Installing Rails on a Mac Shouldn't Be As Hard As It Is
by eipipuz on Tuesday July 10, 2012 @04:26PM
(#4225961)
I agree that there must be a better way, but I need to point it out.
Ruby does come with Mac. Ruby is not Rails. The default installation allows anyone to try Ruby.
Re:Installing Rails on a Mac Shouldn't Be As Hard As It Is
by nicholassmith on Wednesday July 11, 2012 @04:46AM
(#4228416)
Sure, and if it's nicely sandboxed away and running in a bubble then it's perfect, if however it requires hooks into the system, which is the current paradigm, then they can't cover all cases. What if you have a custom bash profile and it kills it? Or some mix of packages throws a curve ball? At the end of the day you should know your system and requirements more than a faraway team, which reduces the risk.
Re:Installing Rails on a Mac Shouldn't Be As Hard As It Is
by krschultz on Tuesday July 10, 2012 @03:22PM
(#4225623)
But is RVM really that hard? If you are on a major distribution of Linux or OSX, all you have to do is install the dependencies and then copy and paste the bash command that setups up RVM.
The hangup is usually installing the dependencies. I remember on Ubuntu this involved hunting down one library that wasn't listed on the RVM wiki. Maybe that needs to be fixed with either more documentation on the RVM wiki or a Ubuntu RVM package (that package probably already exists).
On OS X it requires getting GCC to work, again maybe that needs to be clearer on the RVM wiki.
On windows - well on windows I just install a Ubuntu VM and go back to that installation.
But fixing those simple things (documentation, possibly RVM package) is far easier than creating a whole new installation process.
Well the default installation shouldn't. The default installation should be for someone who just wants to try Ruby out, that will just set things up to work, and won't interfere with anything else on the system (except for integrating with the webserver you're using). Like PHP does. Then they can mess around with Ruby, and as they learn about it, go back and change the installation or re-install as necessary.
> Do you trust an automated installer to be able to do it reliably on every single machine?
Well, yeah. Isn't that what installers are for? They're written by the team that developed the software. I assume they have a much better idea of how to properly install it than I do!