Given that version 1 landed as "VitePress" they probably decided to keep the name.
> I initially gave VitePress a different name because I wanted to be able to explore a different architecture without worrying about backwards compat. After shipping the vuejs.org with VitePress, I believe VitePress is flexible enough to be a full replacement of current VuePress while offering better DX and better performance.
> ...
> I think we should ship VitePress stable as VuePress 3, but I am open to potential questions and concerns.
> Pros: Less confusion in the long run. There will be just one officially maintained SSG with better DX, better performance, and customization that fully aligns with standard Vite-based Vue apps.
> Cons: Potential confusion in the short run, since there are probably a lot of tutorials / integrations targeting VuePress 1. Still I think with the recent Vue 3 switch, users won't be surprised with a major upgrade for VuePress.
> producing many copies by repeated direct impression
And VuePress might turn off people who are React devs for example.
What happened instead was… they essentially forked Vuex, renamed it Pinia (thus no longer even being at first glance related to Vue, or the Flux pattern it sort of uses).
The reasoning was illogical, something about worried people would be confused with its new API. Well I’ll take that to the next level and point out they didn’t simply fork and rename Vue when they released a new major version.
This led to very poor discoverability for sometime, I don’t know if that’s still the case as I decided to use React not longer after this because of all the nonsense in Vue.