> I kinda get this, the "framework maintainers are superhumans who write amazing code and nothing I could write could get close to that" attitude. As had been

> I kinda get this, the "framework maintainers are superhumans who write amazing code and nothing I could write could get close to that" attitude. As had been pointed out before: they don't have to be much smarter, they just have to have more time at hand or be more people, get more bug reports, get more improvement ideas etc. > But the framework maintainers aren't looking at your specific situation. I mean sure, if you're writing yet another CRUD system for yet another SaaS product, then fine, use Rails, that's what it was designed for. Let me assure you that I am not using Rails for my hypothetical real time radar tracking system and I'm not recommending anyone else using it for anything either except what it is made for ;-) That said I think many people will find that their use cases aren't that special. > But if you're not building Basecamp, then your application is eventually going to want to do something that Rails wasn't intended to do. And then you're going to have to write your own code. Did you ever try Rails? > And if you're not confident that you can write that code, because you don't think you can write good enough code for this... then... why are you doing this? This is a very uncharitable interpretation IMO. Maybe we just have better things to do than reinventing the wheel again right now..? (To be clear: sometimes the wheel needs to be reinvented, but every single time.)