![]() In five years of using Ruby, I’ve had exactly zero problems with this behavior. So, you might be thinking: Can everybody and their mother mess up my precious application? While this behavior indeed looks scary–it’s really not. Just like that, we’ve introduced an error into the String class that could be wrapped into and obscured by layer upon layer of complexity. This particular error would be easy to spot, but things can get much more sinister: class String It’s that easy: with just five lines of code, we’ve taken an existing class and overridden its behavior. Let me illustrate with some monkey patching: "1".to_i They worry about what might happen with all the freedoms that Ruby allows, all the potential for misuse. While most developers agree that Ruby is handy, some see it as too much so. ![]() So, why use the Ruby on Rails framework? Ruby makes programmers happy, as advertised. Ruby somehow enables programmers in a special kind of way that is so hard to explain to the ‘unwashed masses’. What he saw back then, many others can see today. The fact is: the author of Rails picked Ruby deliberately, and his ‘wild’ bet paid off with huge interest. I can’t say for sure whether or not that’s true, but I do know that it would be a huge shame if the world missed out on such a superb language. Some people like to belittle Ruby by saying that it’s “so easy for Ruby” with its “knight in shining armour called Rails” and that without Rails, “Ruby would be irrelevant”. It’s possible that nobody would even know about the benefits of Ruby if it weren’t for Rails itself. Why Ruby on Rails? I’ll try to explain what, in my opinion, makes Rails beneficial enough to be seriously considered for a plethora of projects and needs. In fact, I believe that most clients know their options just fine and yet they still decide to go with Rails. When you think a bit about it, it does not seem right to think that a person that is giving me money to build things is somehow limited and ‘just doesn’t get it’. “They don’t even know what they’re asking for,” they say.įor us as programmers, sometimes it does indeed seem like our clients don’t have a clue. Then they pull out something similar to this amazingly ignorant comparison between Git and PHP to prove their point. If they’re recruiters, they almost feel sick in the stomach about having to find yet another Ruby on Rails ‘primadona’ developer. Sometimes I hear people complaining about their clients, saying that they insist on using Rails, that they’ve had too much Kool Aid.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |