rfcs VS vitesse

```

We started experimenting with this ling of thought almost 3 years ago:

- First take (ref sugar), Nov 2020: https://github.com/vuejs/rfcs/pull/228

- Take 2, Aug 2021: https://github.com/vuejs/rfcs/pull/368

- Take 3, Nov 2021: https://github.com/vuejs/rfcs/discussions/369

We provided it as an experimental feature and had a decent number of users trying it out in production. The feedback wasn't great and eventually decided to drop it. https://github.com/vuejs/rfcs/discussions/369#discussioncomm...

This is a personal preference, but I use ref almost all the time. Despite tediously writing the .value to access the ref’s value, the Vue team is aware of the problem, and the open RFC - Reactivity Transform, was aiming to solve this issue, however, seems like it was abandoned.

This was a good change. Evan has always been extremely good at putting his finger on the pulse of the frontend community. If there's a feature or paradigm that people love that would fit in Vue, Evan will incorporate it. Over the years, Vue has implemented (and sometimes later deprecated) dependency injection, JSX support, custom elements, Angular-style class components, Svelte-style ref sugar, and now Solid-inspired compiler optimizations. They even changed the order of a Vue file to match that of Svelte: first the script, then the template.

Here is the Current language: https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs/0000-function-api.md

So here's the bottom line. You get RFCs looking like someone trying to land a man on the moon for things like generics in vue while the rest of the world gets work done. Eg https://github.com/vuejs/rfcs/discussions/436

Oh you meant that. Vue and Vite got amazing documentations and I recommend to read them through fully. One more thing i can also recommend is to read through Vue RFCs as well as they contain more extra info sometimes not covered in the docs: https://github.com/vuejs/rfcs Since Vite is based on Rollup, I'd additionally recommend to read Rollup docs, but I find it quite hard to read and navigate https://rollupjs.org/guide/en/#big-list-of-options

The Reactivity Transform, the way it is, is a fucking mess, and would introduce a lot of confusion into the already confused Vue 3 syntax.

https://github.com/vuejs/vue-router/issues/703 https://github.com/vuejs/rfcs/blob/master/active-rfcs/0036-router-view-route-prop.md https://github.com/vuejs/vue-router/issues/703#issuecomment-428123334

Not a "huge drawback", but the excess of .value is annoying. The Reactivity Transform RFC attempts to mitigate that, but IMO it's a footgun and will make things a lot more confusing, so I hope it's not merged.

For Vue 3, not so much. It not only introduced new different concepts, but also made a huge mess for newcomers with its variations (Options API, Composition API, Composition API with script setup), which are different but similar enough to be confused. And the upcoming Reactivity Transform will make it even more confusing by introducing new variations.

The docs help but also look at vitesse template - that helped me a lot to figure out usage and the author of the template is one of the contributors of unplugin.

Although, I think admin templates are overrated, a setup template is a lot more useful, check out: https://github.com/antfu/vitesse

Vitesse

Even with something like Vitesse: https://github.com/antfu/vitesse?

Also, if you use Vite, there's a cool starter template called Vitesse. I generally use the lite version, (less packages) called Vitesse Lite.

I think this is exactly what you are looking for: https://github.com/antfu/vitesse