3 ms·

Not the most important thing in the world but I'm surprised this is named VitePress when it uses Vue and is apparently replacing a project named VuePress. Surel

Not the most important thing in the world but I'm surprised this is named VitePress when it uses Vue and is apparently replacing a project named VuePress. Surely the latter is the more appropriate name? I could make a static site generator with React or Svelte or whatever that also uses Vite.

addicted 3y ago
Maybe because Vite has a broader audience than Vue. And VuePress might turn off people who are React devs for example.
ayhanfuat 3y ago
There is a discussion related to naming on GitHub: https://github.com/vuejs/vitepress/discussions/548 https://github.com/vuejs/vitepress/discussions/548 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.
amiantos 3y ago
Seems weird to me to name this project after WordPress when it's not really an equivalent to WordPress at all.
- Menu_Overview 3y ago
  I think the etymology for both of these kinda comes from "letterpress". > producing many copies by repeated direct impression
lloydatkinson 3y ago
Unfortunately the Vue ecosystem has gone through several poor names for its libraries. One example is its state management library, Vuex. When it came to a new major release which would normally be a major version bump semantically, right? 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.
- deleted 3y ago
  [deleted]

addicted 3y ago

Maybe because Vite has a broader audience than Vue. And VuePress might turn off people who are React devs for example.

ayhanfuat 3y ago

There is a discussion related to naming on GitHub: https://github.com/vuejs/vitepress/discussions/548 https://github.com/vuejs/vitepress/discussions/548 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.

amiantos 3y ago

Seems weird to me to name this project after WordPress when it's not really an equivalent to WordPress at all.

Menu_Overview 3y ago
I think the etymology for both of these kinda comes from "letterpress". > producing many copies by repeated direct impression

lloydatkinson 3y ago

Unfortunately the Vue ecosystem has gone through several poor names for its libraries. One example is its state management library, Vuex. When it came to a new major release which would normally be a major version bump semantically, right? 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.

deleted 3y ago
[deleted]