tag:blogger.com,1999:blog-20616594.post-63765093151285901242007-09-23T20:32:00.000Z2007-09-23T21:13:19.268ZAs I'm doing a lot of PHP at the moment, I'm following PHP news with interest. But <a href="http://www.oreillynet.com/ruby/blog/2007/09/7_reasons_i_switched_back_to_p_1.html">7 reasons I switched back to PHP after 2 years on Rails</a> is interesting for Eiffel programmers as well. For example:<br /><blockquote>I was nearly killing my company in the name of blindly insisting Rails was the answer to all questions, timeframes be damned.<br />But when I took a real emotionless non-prejudiced look at it, I realized the language didn’t matter that much.<br />Ruby is prettier. Rails has nice shortcuts. But no big shortcuts I can’t code-up myself in a day if needed.<br /></blockquote>Update, one more observation I couldn't agree with more:<br /><blockquote>Speaking of tastes: tiny but important thing : I love SQL. I dream in queries. I think in tables.<br />I was always fighting against Rails and its migrations hiding my beloved SQL from me.</blockquote>Although I prefer <a href="http://www.pobox.com/%7Eberend/xplain/">Xplain</a>, the issue is the same. All that active record, hiding the database, somehow making it object oriented, is a complete waste of energy. Databases and objects are two different worlds. Storing objects is possible and can be abstracted nicely. Then try to do fast searching, combining data, data warehousing, and that nice little object oriented world falls apart.Berend de Boerhttp://www.blogger.com/profile/11433622686361556089noreply@blogger.com