By CodeJustin
via blog.alieniloquent.com
Published: Nov 19 2009 / 12:49
I’ve been coding in Ruby for a long time, and I love the language. It has all the object-oriented power of Smalltalk, the functional power of Lisp, and the concision of Perl. It is so powerful that it enables programmers to devise entirely new ways of writing software, and that is the hallmark of a good language.
The trouble is that some of these new ways of programming aren’t good ways of programming. Over the last five years we’ve seen the ascent of Ruby on Rails and the Rails Way of doing things. I’ll be the first to admit that Rails revolutionized web development. But it has taught an entire generation of web developers to think like a cargo cult, and that’s not good.
-
FlashDevelop and ActionScript 3 - how to embed image - fast tip
-
Startups pass on Silicon Valley to find their fortunes in New York
-
PHP 5.4 Traits, Closures, and Prototype-based Programming
-
A Beginner’s Guide To jQuery-Based JSON API Clients
-
HTML5 local storage 1-2-3
-
RubyInstaller for Windows: The easy way to install Ruby on Windows
Comments
planetmcd replied ago:
Good read. I would suggest that the same power in the rails/django model of enabling rapid development that can be a boon for many, can also be a burden for some. If the challenge in your webapps, was mastering all the details needed to get to a decent web application out the door, and suddenly that skill is more of a commodity, that can either allow you to work on more difficult/interesting problems, or take away the interesting challenge of your work, or even your work all together.
Some what analogous to the Luddite's problem.
Voters For This Link (12)
Voters Against This Link (1)