Another day, another post taking an extreme position on Ruby/Rails, well no wonder given the author. While such articles keep getting votes, clicks and attenti

Another day, another post taking an extreme position on Ruby/Rails, well no wonder given the author. While such articles keep getting votes, clicks and attention, they often take an extreme position which does not always result in some useful takeaway. There is no point to argue that rails is some silver bullet because such things do not exist. The whole rails issue is pretty damn simple. There are applications where rails is an amazing fit. Simple, one off CRUD apps is probably the primary example and rightfully so. At the same time, there are complex applications where rails might be a questionable fit and some other, maybe more transparent and more explicit, frameworks might work better, which depends on a lot of factors. The 2.days.ago example is a good one to illustrate this point. If you are a software shop and your client wants some trivial CRUD application, these kinds of shortcuts are great. A significant share of software projects are just like that and there's no shame in it, there's no point to overengineer. On the other hand, if you are working on a large project, with many developers working on the code, you need to be really careful with those so that it doesn't get out of hand.