docs-next VS rfcs

Also, regarding the docs, the problem with the toggle is that the preference it is set client-side. So when you're answering a question on SO and trying to send someone to the docs, you have to explain how to switch to composition. (https://github.com/vuejs/docs/issues/1901 and https://github.com/vuejs/docs/issues/1482)

Accessing the config and global objects is technically possible but is highly discouraged as it is considered an internal API: https://github.com/vuejs/docs/issues/1422

My Feature Request got accepted and Even You already changed the behavior: https://github.com/vuejs/docs/issues/1562

It's all open source on github: https://github.com/vuejs/docs

Yep! https://github.com/vuejs/docs/tree/next

🍔 Simple Vue 3 wrap for Supabase.js Client build with Vitejs

```

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.

To stay updated, follow the RFC at https://github.com/vuejs/rfcs/discussions/503.

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.

Now the $on has been removed, but the event subject is causing some confusion, see: https://github.com/vuejs/rfcs/discussions/397

The RFC has shown that this feature is very controversial, with lots of implications. Personally, I liked it at first, but now I'm against it.

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

Plus, even that there is a real possibility that the controversial Reactivity Transform RFC leads to a Vue 4 version, it is likely to bring just minor breaking changes from Vue 3.