There was absolutely no reason Pinia couldn’t have been Vuex 5.
I raised that point more than once and was always given the lamest reason for it.
They believed people would be “too confused” with the breaking changes in the new API.
This was always a dumb explanation. That’s what major versions are for - breaking changes. Of course upgrading from Vuex 4 to 5 would involve refactoring code.
Pinia is of course mush better and has real types. But they did themselves a huge disservice by not making that Vuex 5. That lack of focus on cohesive framework options and senseless deprecation of already established libraries is the major problem.
Sorry for being reductionist. I will try to do better. But you literaly say you are happy with the API changes from Vuex to Pinia, so it is unclear to me what you dislike apart from the name change?
I don’t work on Vue itself and cant speak for that team. I’m a developer who use both Vue and React daily and seem to be an exception in that I rather like both, while recognizing both have different strengths and weaknesses (I have also tried other frameworks like Angular which i didn’t like).
I raised that point more than once and was always given the lamest reason for it.
They believed people would be “too confused” with the breaking changes in the new API.
This was always a dumb explanation. That’s what major versions are for - breaking changes. Of course upgrading from Vuex 4 to 5 would involve refactoring code.
Pinia is of course mush better and has real types. But they did themselves a huge disservice by not making that Vuex 5. That lack of focus on cohesive framework options and senseless deprecation of already established libraries is the major problem.