11–20 of 49 posts
Earlier quoted context omitted.
This may be a source of confusion. In most circles, release candidate signifies that this should be the final release, and will only be changed if new bugs emerge.
s/Most/All/. I've never heard of a release candidate meaning anything else, it's something you'll release as-is with a non-rc version unless critical bugs emerge. This is a beta, not a RC.
For new RoR programmers, is it recommended to just start in with Rails 3, or stick with Rails 2 until Rails 3 "stabilizes"? There are a bunch of Rails 3 books out there; do they generally line up well with this release candidate, or are they full of old information that a new RoR programmer would stumble upon and not understand how to fix? [EDIT] The three books I saw available that specifically mention Rails 3 in th…
For new RoR programmers, is it recommended to just start in with Rails 3, or stick with Rails 2 until Rails 3 "stabilizes"? There are a bunch of Rails 3 books out there; do they generally line up well with this release candidate, or are they full of old information that a new RoR programmer would stumble upon and not understand how to fix? [EDIT] The three books I saw available that specifically mention Rails 3 in th…
For new RoR programmers, is it recommended to just start in with Rails 3, or stick with Rails 2 until Rails 3 "stabilizes"? There are a bunch of Rails 3 books out there; do they generally line up well with this release candidate, or are they full of old information that a new RoR programmer would stumble upon and not understand how to fix? [EDIT] The three books I saw available that specifically mention Rails 3 in th…
If you have an older book using an older version of rails, DON'T use Rails 3, use the version used in your book (DHH mentioned this on an episode of coderpath http://coderpath.com/posts/1)
For new RoR programmers, is it recommended to just start in with Rails 3, or stick with Rails 2 until Rails 3 "stabilizes"? There are a bunch of Rails 3 books out there; do they generally line up well with this release candidate, or are they full of old information that a new RoR programmer would stumble upon and not understand how to fix? [EDIT] The three books I saw available that specifically mention Rails 3 in th…
I got "rails 3 way" and "agile rails 4.ed". rails3way is pretty much a complete rewrite; its only 266 pages filled so far, but looks good. Agile rails is more finished than rails3way. They are both pretty good books, but if you want more of a "completed" book, agile seems to be the one closer to that. I'm learning RoR from scratch too. The recommended setup is to use ruby 1.9.2. Your first question really depends on…
As far as 1.9.2, if you plan to do deployment (Even for testing) any time soon on Heroku (the coolest, if not the best hosting solution for Rails) then you may want to kick back to 1.8.7, because Heroku won't support 1.9.2 until a final is released.
For new RoR programmers, is it recommended to just start in with Rails 3, or stick with Rails 2 until Rails 3 "stabilizes"? There are a bunch of Rails 3 books out there; do they generally line up well with this release candidate, or are they full of old information that a new RoR programmer would stumble upon and not understand how to fix? [EDIT] The three books I saw available that specifically mention Rails 3 in th…
As far as whether 2.3 or 3.0 makes the most sense at this point, it depends. Personally, I have been working on a brand new project that I started with 3.0 beta 1 and haven't ran into any major headaches. That said, since you're new there is a lot more information out there regarding 2.3 (be careful, some is much older).
To give you some better advice, why are you getting into Rails? Are you trying to get a project started/out the door/etc, or simply looking to learn it because it looks interesting/fun?
For new RoR programmers, is it recommended to just start in with Rails 3, or stick with Rails 2 until Rails 3 "stabilizes"? There are a bunch of Rails 3 books out there; do they generally line up well with this release candidate, or are they full of old information that a new RoR programmer would stumble upon and not understand how to fix? [EDIT] The three books I saw available that specifically mention Rails 3 in th…
"We’ll be making sure we get performance of Active Record back to at least 2.3 levels before release." Why call it a Release Candidate if you still plan on tweak more stuff?
I don't think you are supposed to question DHH or what his name is.
Help me be a better HN commentator, please.
Earlier quoted context omitted.
I don't think you are supposed to question DHH or what his name is.
Wow, ok. It was an attempt at humor. So now my question is is HN not the place for that? Or do HN folks generally get behind RoR? Or...do I just need to be more thoughtful and not thoughtless in my postings? Help me be a better HN commentator, please.
Earlier quoted context omitted.
I don't think you are supposed to question DHH or what his name is.
Wow, ok. It was an attempt at humor. So now my question is is HN not the place for that? Or do HN folks generally get behind RoR? Or...do I just need to be more thoughtful and not thoughtless in my postings? Help me be a better HN commentator, please.