1. Scofia says:

    Michael: Just to clear up a few things for you.1- Traceability. This rlelay boils down to your design, if you're using yield statements to solve a specific problem, then you're most probably barking up the wrong tree. Generally, yield serves to allow the calling code to do whatever they want, without caring about what is done.3- Too clever one liners. In a rails app, clever one-liners belong to models/helpers where they can just as cleverly be hidden away and documented. I agree with you though that code like this can/will become incomprehensible.5- Obnoxious advocates. Every language/framework has its fair share of these people =) I'm not defending DHH but Dreamhost is a pretty childish host as well, especially in how they handled one of their recent billing crisis. Plus, overcoming hurdles and solving problems like these are part and parcel of any business; Dreamhost will have to deal with it.Also, I agree with you on how sucky documentation is for RoR. But look at the upside, sometimes being forced to look in the source code makes you learn to write better code (arguably).Eduardo: I would disagree with you that RoR is easier than other frameworks therefore it requires less competent programmers. Looking at how things have become, C#/Java programmers are a dime a dozen and the bulk of them aren't truly programmers. Yet they get by in their jobs, copy/pasting from codeproject (or through similar devices, bear with me).This isn't something you can do in Rails without running into a wall. The thing is, a lot of problems have already been solved by the ASP.net/Java/etc community whereas in RoR, you can sometimes find yourself dealing with a problem alone.I would say that it's easier to write a web app in RoR than ASP.net/Java if you were a competent programmer, but the lack of market penetration makes it harder for the below average programmer. Same goes for Python.

Post a comment

Name or OpenID (required)


(lesstile enabled - surround code blocks with ---)