Marnen Laibow-Koser wrote in post #955845: > Then why are you using Rails? Rails forces (OK, strongly encourages) > you to fit the server-side part of your application into its > predetermined architecture. I think this is a Good Thing, because I > think its architecture is well designed. It's also loose enough to be > generic -- a neat trick considering every application is different and > has different needs.
I use Rails because I also believe in the adage of "decisions are bad." The fewer I have to make as a developer the happier I am. "Everything has a place, and everything is in its place." This is a gross exaggeration, obviously, but is intended to present an ideology. Speaking of pet peeves; I suppose my responses are a side effect (or is that side-effect? Ahh! Who really cares?) of too much time in enterprise application development. I feel inundated with an insane number of mostly meaningless acronyms and buzzwords. I fully recognize the need for both creating, and putting names to, design patterns. But, there are limits to how much of that I can stand. -- 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.
