Hi Evan, I think you make a valid argument which holds true, until a certain scale.
After a certain size you need to start thinking how to better organize your app using patterns and best practices. This has the advantage of slowly decoupling you from the framework itself. It won't be 100% possible of course but it would increase time spent on business logic and probably testability and quality.
In the end this will let your framework do what is supposed to do and your app solve the business requirements.
How to get there? Experience. In the meantime I don't think there's anything inherently wrong in choosing an opinionated framework like Rails. Plenty of companies built successful businesses around it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Evan, I think you make a valid argument which holds true, until a certain scale.
After a certain size you need to start thinking how to better organize your app using patterns and best practices. This has the advantage of slowly decoupling you from the framework itself. It won't be 100% possible of course but it would increase time spent on business logic and probably testability and quality.
In the end this will let your framework do what is supposed to do and your app solve the business requirements.
How to get there? Experience. In the meantime I don't think there's anything inherently wrong in choosing an opinionated framework like Rails. Plenty of companies built successful businesses around it.