[huuggjkkkk]

Good luck getting any libraries working. Good luck using graphql. Good luck getting the tooling stable. Good luck getting a PR on the main code base done. Vue in production is a minefield of nightmares.

Rather have Facebook as a single point of failure than some random dude who has other things that consume his interest.

[codefreakxff]

Are you trolling? I’ve used Vue in a couple of projects and honestly have no idea what you are talking about. Feel free to expand on your statements. Otherwise this message doesn’t fit in hn

[avaldes]

The shift to Vue3 and a new paradigm (composition API) left the community in a state of confusion of where/how/when to migrate. The old paradigm is still supported but more like a legacy layer than the way to go. It reminds me of the python 2-3 schism.

[mariocesar]

I'm part of the community, several big production projects, several migrations from v2 to v3.

I was never confused.

The backward compatibility has a clean plan. For the bits that were complex changes, it was possible to do partial upgrades. From the beginning, the partial upgrade was in consideration. There was always early documentation, and you have access to v3 in alpha and beta all the time with complete documentation and complete guides. You also have standalone packages to start testing migrating bits of v3 to v2, like the composition API, class components, etc. It was one of the most seamless transitions I experience.

[Rapzid]

I'm not sure a lot of people realize just how much a lot of the ecosystem relies on and is constrained by Evan