3 ms·
I don't want to be surprised by a framework. http://dev.rubyonrails.org/ticket/10919 http://dev.rubyonrails.org/ticket/10919 The above bug report (while incre
by parfe 16y ago
I don't want to be surprised by a framework.
http://dev.rubyonrails.org/ticket/10919 http://dev.rubyonrails.org/ticket/10919
The above bug report (while incredibly funny) was a symptom of what turned me off while learning rails. Why would tables be pluralized automatically? A model might change to a word I didn't even know is the correct plural. ( I didn't go any deeper than tutorials. )
Overall I prefer Django as nothing comes as a surprise, and the shortcomings aren't a huge bother for what I do.
- generalk 16y agoWhy should be tables be pluralized automatically? Because that's frequently how you'd do it anyway. I deal in a lot of legacy data stores, and I have a lot of "set_table_name" calls. That said, Rails is opinionated, and not agreeing with those opinions seems like a perfectly valid reason to not like it.
- JangoSteve 16y agoIt's beneficial to point out that ActiveRecord is no longer tied to the hip of Rails. In fact, in Rails 3, you now have ActiveModel which gives you all the "Active" goodness of model objects without connecting to a specific database at all. In other words, issues like this are no longer a problem in Rails, maybe just in certain modules you can install and use optionally in Rails.