If you're working with a framework or tool, you should be as idiomatic as possible. Follow the best practices of that tool. It's not because you can't do it bet

If you're working with a framework or tool, you should be as idiomatic as possible. Follow the best practices of that tool. It's not because you can't do it better, you might be able to. The reason is because when someone inherits the project from you or you need to onboard someone, all of their prior knowledge will apply to your build, and all the documentation and help forums for that tool/platform will actually apply to your project. Part of this is ego I think. Many of us have landed jobs in agencies or at companies who produce commodity software using a framework or tool, and we see things about them that we feel we can do better. But if you're working with a client and they've decided on a framework, part of that decision is the implicit understanding that you will build them a platform that every developer using that framework can work on. It's not unlike choosing to use Volkswagen vans for a transport business because you have a good community of Volkswagen mechanics. If they ask you for a VW, and you give them a VW that has a Ford engine and a Nissan transmission, they're going to be pretty confused and annoyed when the mechanics tell them they can't work on this and need to rebuild it.