Do you really want a single-page application framework?
I find that when you start rolling your own framework, you just end up making crappier versions of what's in Angular, Ember, etc.<p>What's worse, a custom framework won't be known by any new developers, so you'll have to spend more resources onboarding them than, say, if you just had to show them how you're using Angular in your company (i.e. they'll already understand things like directives, components, etc.)<p>Finally, you lose the advantages of having an ecosystem of plugins, support, etc.<p>It just doesn't make any sense to me to roll your own. Any initial speed you gain you end up paying for later on. To me, using something like Angular means I can harness the experience and expertise of dozens of superstar coders at Google whose only job is to think about the best way to write SPA frameworks.<p>Why would I not take advantage of that?