On Tue, Mar 24, 2009 at 4:17 PM, Fidel Viegas <[email protected]> wrote: > In other words, either one will be ok for a beginner.
That's my point exactly. But the switch to sqlite was touted as "SQLite3 is simply an easier out of the box experience than MySQL". http://weblog.rubyonrails.org/2007/12/17/rails-2-0-2-some-new-defaults-and-a-few-fixes Sadly, the statement actually carries weight _if_ you wrongly assume all new Rails interest will come from Mac owners. > I don't really know about the research world, but I do know that in > the commercial world, it is sometimes necessary to show a quick > prototype in order to convince a potential client. Convince them of what? That pencil and paper or a simple wireframe app isn't good enough? It's been my experience clients want to see your past work and talk to your references. They care not for how fast you can scaffold an app together at Starbucks. > There is, though, one thing that I happen to agree with you on one of > your previous posts: that we should have better support for other > RDBMSs. That would be really nice. Yup. Assuming everyone uses the same thing is an obvious mistake to anyone giving it more than a moment's thought. I can only imagine how many times "Works on MySQL, ship it!" has probably been declared at 37signals. -- Greg Donald http://destiney.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 -~----------~----~----~----~------~----~------~--~---
