News for hackers. Stuff that matters.
Re:How two Pythonistas accidentally fell in love with Rails by btilly on Monday September 13, 2010 @06:30PM (#1688587)
"Dislikes" may be stronger than you want, but would you agree if it were changed to "recognized shortcomings"?

Let's use Ruby for an example. You discounted performance because it never matters in web development. Fine. Here are 5 more issues that do come up in web development. Not using native threads makes it easy for a poorly coded C extension (for instance a database driver) to block all threads. Common classes of errors (eg typos in variable names) can only be caught at run-time. Some widely used libraries use monkey patching, and with dependencies it is very easy to pull one in without realizing it, only to get burned later in what should be an unrelated library. By default gem does not run unit tests at installation, which makes it less likely that developers will get prompt feedback about issues like platform-specific code or unspecified dependencies. While mix-ins are convenient, they provide opportunities for conflicts and make it harder to track down the source of a method when you're trying to debug something.

I don't even use Ruby very much. If I did, I could easily come up with a much larger list. (My primary language is Perl. You should see the list of complaints I have about it! Yet I still like it. And for the record I like Ruby as well.)

Edit: I only included 4 issues initially, so I just added another.

Re:How two Pythonistas accidentally fell in love with Rails by _pius on Monday September 13, 2010 @06:44PM (#1688628)
"Dislikes" may be stronger than you want, but would you agree if it were changed to "recognized shortcomings"?

Yup.