Seriously?
If your application become sufficiently complex that it can't be easily grokked by a decent dev, that's when you know it's time to switch.
Until then it's just over engineering (which the JS community admittedly loves).
If your application become sufficiently complex that it can't be easily grokked by a decent dev, that's when you know it's time to switch.
Until then it's just over engineering (which the JS community admittedly loves).
I estimate that every 20% that a codebase grows it needs some amount of refactoring. Definitely anything that moves from skunkworks to production will need some pretty heavy rewrites, and will probably need a framework that better meets its newer needs. The question is how much cost was sunk in getting there. The refactor will have to happen no matter what.
Guy A believes his custom design is simple enough to comprehend by anyone. Guy B doesn't agree.
It doesn't really matter at the end of the day. If you work in a team environment, the toolset will be pre-determined already. You don't have a choice.