Phlip wrote: > Wayne Molina wrote: > >> ...the community >> seems to have charged forward and changed its best practices, so it's >> just added a whole bunch of things I need to learn as well. > > The more things change, the more they stay the same.
As usual, Phlip has some excellent advice here. I thought I'd just amplify a few points. > >> For instance, the new thing seems to be BDD and RSpec, so I have to >> learn RSpec in addition to Rails and Ruby. > > What's 10-years-old about that is "test-first". Write a test that fails > before > writing _any_ line of code. Yup. And that's not a Rails-specific thing either. [...] > Also, while RSpec is in a growth phase, I suspect most Rails tests are > in > Test::Unit. I suspect you're wrong. I know that you don't like RSpec (for reasons I cannot fathom), but it seems to me that most Rails code I look at these days uses it. > Learn it. Er...why, other than for completeness' sake? Last time I looked at Test::Unit, it just seemed so *clunky* compared to RSpec, although your assert2 module seems to help. > > > Git is used for version >> control, so that's something else. > > Ideally, put either git or svn into your lib/tasks/project.rake, and > then run > short rake commands. Maybe. I liked that approach with Rubinius, when I was a newbie to Git, but these days, I think I use Git in so many different ways that writing Rake tasks wouldn't really reduce any complexity. I *can* think of one or two exceptions, though. YMMV. > > > RJS is out and unobtrusive stuff >> is in, so that means jQuery. > > Hardly; JavaScript is still JavaScript. Indeed. You can be unobtrusive with any JS library, or with none. jQuery is hardly implied by unobtrusive JS. > > The good news there is the libraries are more pluggable, and as Rails > converges > with Merb they will only get more-so. I have a suspicion that Rails will jump the shark when it merges with Merb, but I would be extremely happy to be wrong about that. > > > Hosting is now typically done with >> Phusion Passenger, so I have to learn Apache and that. > > The story there is, for whatever reason, Ruby for the longest time had > no module > that plugged into the great A-Patchy server. Actually, mod_ruby has been around for a long time, but its single-threaded nature made it unsuitable for Rails. > When it arrived, the > committee > renamed it to Passenger. I don't think that name came from the Apache committee...did they even have anything to do with Passenger? > >> Finally with >> the Rails+Merb merger things are going to get shaken up even more so. > > Merb has a better core. Good to know. > >> I really want to learn Rails but the community seems to just keep >> jumping from one bandwagon to another Yes, parts of the Rails community are very faddish. It's up to you to decide which fads are worthwhile. :) > without staying put long enough >> for somebody who didn't come aboard in 2005-2006 to ever get to >> speed. > > Doing Rails requires good skills with El Goog, including codesearch, > including > remembering to always check the date on some blog entry offering some > critical > tidbit of information. Yup. Rails core development moves quite fast. > > Any Rails book, plus that skill, will keep you in the loop. Seems to me that Rails books are generally out of date as soon as they're printed. > > And the other good news is as Rails matures, gains converts, and becomes > stable, > the committee won't be able to make all these changes so often. That is > the > intent of the Rails-Merb merger. Do you really think that DHH will be able to resist the lure of further opportunities for intellectual masturbation by tinkering with the Rails core? I sure don't. [...] > Anyone who invents a better Rails wins, so the > competition > keeps us honest, even as we invent conflicting libraries and systems. We'll see. 3.0 may be a better Rails, or it may not. > > -- > Phlip > http://flea.sourceforge.net/resume.html Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
