[bird_monster]

> I think this is a good thing generally, Vue has consistently been one of the best engineered and most effectively designed pieces of software in the Javascript world, largely due to uncompromising enforcement of the design opinions and aesthetics it asserts.

Which is much easier to attain if you're comfortable with only a single person being allowed to write code. Personally, I wouldn't use Vue in any business-oriented application for this exact reason. The "bus factor", or as I would call it, "If and when Evan decides to stop caring about Vue", is enough to make Vue dead in the water as a legitimate FE library choice (to me).

[feoren]

This is why you should always avoid every giant "do everything" framework. Use libraries that are small, focused, and do their one job well enough right now. Then it doesn't matter if it stops being maintained: it still keeps doing its job well. If you do have to replace it, it's much easier, because it doesn't do too much. Vue, Angular, React -- all of them are "build your application around our framework" libraries, not "easily incorporate our library into your workflow" libraries. That is enough for me to immediately reject all of them.

[that_guy_iain]

The org has 49 people on it. And every project that has one people who leads it can surive without that person, it's called they fork the project.

[bird_monster]

https://github.com/vuejs/vue/graphs/contributors?from=2016-0...

Here you can find the code additions Github Insight.

The org can have 49 people in it, but 48 of them are not writing code for Vue.js.