With Vue, even though it is not backed by a Facebook or Google, we have to acknowledge a couple of drivers to Vue’s success. Massive support from the Chinese community. More importantly, being bundled with the Laravel PHP framework (since version 5.3 of Laravel, I believe) also helped (that is how I first heard about Vue). And Evan also used to work at Google and marketing wise, it makes for good marketing when you can say, “Created by an ex-Googler”
In the end, it all comes down to marketing. For Aurelia 2, I am going to make it my mission to organise training, conferences and numerous events around Aurelia 2. People seem to forget that while Vue 1 had some success, it wasn’t on anyone’s radar really until version 2 of Vue came out.
Sadly, for Aurelia 1, it was all a case of bad timing. We debuted when ES2015 was barely supported, transpilers were in a state of flux (TypeScript was not that popular), Babel had not long rebranded from 6to5, Weback was continually putting out breaking releases, JSPM looked like a sure bet and numerous web specifications were in their infancy (Object.observe, Shadow DOM).
Aurelia tried pushing the envelope and developers were not ready for the futuristic vision of Aurelia. We also made the mistake of debuting Aurelia with no documentation followed by a period of rough turbulence where the documentation was lacking, this I believe really set us back.
The timing is right for Aurelia 2. The front-end landscape has settled, TypeScript is growing in popularity and seems like a safe sane bet. The design of Aurelia 2 means smaller bundles, less issues with tooling, better configurability, better performance, better documentation and more future proof.