What backlash against Vue 3? I know that there were very passionate discussions about several different RFCs that eventually lead to the current Composition API. But as far as I can tell, the current Composition API is very well accepted in the community. Also, the Composition API is an addition and does not replace the API of Vue 2.
So do you refer to the controversies about older RFCs? Because I can't see any other backlash. BTW, having discussions in an RFC is a good thing as it helps getting to a better overall solution.
> creation of Svelte
How is Svelte related to Vue in general or Vue 3 specifically? Svelte 1.0 was released in 2016 and I can't really see any irony here at all.
I don't know much about Vue but the single file components used in Svelte was inspired by Vue.
I think they share more goals than they compete on, with Svelte being newer (compiler based) and Svelte taking an older style approach (Virtual DOM) to implement those goals.
No, I don’t see any irony here. Name one programming language/framework/tool that’s universally game-changing for every single developer. The reality is that technology doesn’t work that way.
The fact that detractors of Vue exist in no way means that Evan doesn’t care about users. It’s very clear that he spent years working on a problem hard enough to build a solid response to React, a project with so much more momentum and money initially.
There was a misunderstanding when documents outlining vue 3 were released. Users thought that advanced functions for component reuse were replacing easy to use existing features. Vue 3 is backwards compatible however, and it was a non-issue. The new features looked great for advanced component builders from what I remember.
