[zzalpha]

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).

[greg5green]

Very few teams have the opportunity to switch later on, and if they do, it's at the expense of the job of the person who chose to go without a framework.

[ChoHag]

If you've allowed your code to grow so far that refactoring is impossible, you have bigger problems to fix than a messy codebase.

[johnnyb_61820]

Everyone has to refactor into new frameworks later on. Going without a framework early on doesn't add an expense, it actually just subtracts one. It is only if they had chosen the framework (and other code decisions) with perfect future vision that this cost would be mitigated.

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.

[jordache]

what is that complexity threshold? Self determined no doubt.

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.