@Sjaak Thanks for the feedback. Lots of good points there.
We were initially thinking to just go with “Aurelia 2” but we didn’t have complete agreement on the team, so we wanted to get some feedback from the community.
To your final point/question, this is an evolutionary step. We’re not building a new framework. It’s the same templating languages, same binding language, same DI, component model/lifecycle, etc. There are breaking changes, but most of them are find/replaceable. This isn’t the same as what the other A* guys did 
For existing Aurelia devs, there will be very little new to learn, and a straight-forward migration path (if you want to migrate). With vNext, you’ll just get something faster, more stable and better tested, backed by better devops, with new features, improved low-level APIs, even more extensibility, improved tooling and integrations, etc. It’s a better Aurelia, not something different.