3 ms·
Dude, take a step back and forget that you know this stuff already and do it professionally. That list is not easy and far from obvious, even for real programme
by sanderjd 15y ago
Dude, take a step back and forget that you know this stuff already and do it professionally. That list is not easy and far from obvious, even for real programmers coming from other environments, let alone for actual programming beginners.
Your list is far from canonical even at this very moment and hasn't even been common for very long. To figure out your list, I have to:
1) know that homebrew is the "right" way to install software that rails depends on, rather than MacPorts or Fink, or the Mac app store, or download.com, and oh yeah, there is this thing called sudo, and I should install homebrew recipes using it, or should I??,
2) know that rbenv and ruby-build are things that exist and that they are competitors to RVM but are either more or less in vogue depending on who I talk to,
3) understand that rbenv doesn't just work in the current shell without closing and re-opening it,
4) know that the "right" version of ruby to use is 1.9.2-p290 (I have to know the patch-number?!) and that I need to install it and set it as my local version (wait, what does that mean, why do I need a local version?),
before I can get around to actually installing rails and using it.
Now, I could just blindly follow someone's list from a blog post (randomly chosen presumably, because the theory here is that I don't know enough about these things to make an informed decision). Maybe I would even get lucky and find a list that works properly with the version of rails that the official documentation is talking about, but it would still be a much better experience by far to go to the official rails site and be told: "hey, download this all-inclusive, up-to-date, guaranteed to work disk image straight from us!".
- rpwilcox 15y agoExactly. It's frustrating. See http://rwilcox.tumblr.com/post/20094754364/its-hard-to-install-rails-on-os-x http://rwilcox.tumblr.com/post/20094754364/its-hard-to-insta.... It's a "story in 20 parts" about what can go wrong with a Raila install on OS X.
- toadi 15y agoActually I agree with previous commenter. These steps are easy and only take like 10minutes and give great power handling versions and gemsets to projects. If you are someone who doesn't know what it means you should learn. Isn't that what a programmer needs to do?
- sanderjd 15y agoThe steps aren't hard, it's knowing which ones to do that is hard. And yes, you should learn what all those things mean and why everyone does them, but it shouldn't be the very first thing you learn.
- moe 15y agoTo figure out your list, I have to No. You have to know none of that. You just have to copy/paste the steps from the rails-homepage (where they should be prominently listed, the lack thereof is the real bug). "hey, download this all-inclusive, up-to-date, guaranteed to work disk image straight from us!" Wait, how is that different from above? Yes, you may be done 2 minutes faster. But you just deprived yourself of at least getting a glimpse on which parts are involved, even if you don't understand them yet. That means you're now even more hopeless when stuff breaks later (and stuff always breaks later). And as a fun fact: Any sane bootstrapper would use the exact same script behind the scenes anyway. There simply is no other way unless you plan to re-invent homebrew and rbenv along the way. I'm really troubled to understand who we're trying to care for here. It sounds like you want to make this Really Easy for absolute beginners who can barely setup a printer. That is a noble goal (for a printer driver), but if you want to teach someone programming then there's a point where you have to stop dumbing it down artificially. And that point is as early as possible. The worst you can do to a newbie is to put him into an opaque sandbox with different behaviors and errors from what the "big guys" are using.
- mgkimsal 15y ago1. Install XCode and homebrew 2. sudo brew install {postgresql,rbenv,ruby-build} 3. Close terminal. Open terminal. 4. mkdir proj && cd proj && rbenv install 1.9.2-p290 && rbenv local 1.9.2-p290 5. gem install rails && rbenv rehash 6. rails new foo ------------------- "hey, download this all-inclusive, up-to-date, guaranteed to work disk image straight from us!" Wait, how is that different from above? ------------------- Really? You really have to ask how those two processes are different? "stop dumbing it down artificially" If (sometimes competing) complexities weren't continually added, there wouldn't be a need to 'dumb it down'. "(and stuff always breaks later)" Wow. Most other web framework communities don't have that much problems with 'stuff always breaking later'. Maybe Rails has reached a tipping point? "There simply is no other way unless you plan to re-invent homebrew and rbenv along the way." Or until someone else does 'reinvent' one of those, and all the cool kids start using it, leaving everyone who learned the 'legacy' way out in the cold without an upgrade path beyond "start over". with different behaviors and errors from what the "big guys" are using I think part of the purpose of the kickstarter project is having one of the 'big guys' behind it. Supposedly that would mean at least one (or more) of the 'big guys' would indeed be using the same process as the 'newbs', reducing this chasm. Sounds like you're threatened some by this - it was hard for you, therefore it should always be hard for everyone for now and forever.
- specialist 15y ago+1 Reading your short list triggered a flashback. I struggled with everything you listed, probably more. When I made a run at getting an existing RoR project running on my Mac (~1 year ago), there was no shortage of howtos and advice. The problem was resolving all the contradictory information. As moe points out, the project home page should have the single source of validated truth on how to get RoR running on a Mac. Minimally. That such a source of truth didn't exist led me to conclude that Rails was run by amateurs and to not be taken seriously.