Greg Donald wrote: > On Tue, Mar 24, 2009 at 2:06 PM, Fidel Viegas <[email protected]> > wrote: > I don't usually write lots of throw-away Rails apps (nor have I ever > met this illusory individual who does), so being able to quickly set > up a new Rails app means nothing to me.
Now you have met that illusory individual. I am a Java developer by day (not necessarily by choice). I use Rails to create "one-off" prototypes all the time. Mostly because experimenting in Java is a complete pain in the a**. > > I work on large apps with lots of tests typically.. so using sqlite > isn't a fast option. > > Configuring a database.yml file is a one-time task, so spending 30-60 > seconds configuring it seems a very small investment considering how > fast my development environment will go from that point on because I > didn't choose sqlite. As I said, I'm not disagreeing with you at all. I was merely providing some insight into the thought process behind making SQLite the default database as I see it. Zero configuration, on this very common Rails development platform, is still faster and more convenient than even the simplest of install/configurations of other databases. -- 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 -~----------~----~----~----~------~----~------~--~---
