rfcs VS vueuse

```

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.

My opinion: Vue, specifically the Vue 3 Composition API. Most of your app state should come from computed() values. Bookmark https://vueuse.org and come back to it often. Go through VueUse's source (the docs for each function link to their source): you'll be surprised at how simple most of it is, and it stands as documentation of best practices for using the composition API in general.

Now, let’s talk about Vue! Once again, we’ll use an external library to handle dark mode simply and quickly. In this case, the library is called VueUse, and you can install it using the command npm i @vueuse/core --save.

Great library. Could use some improvements as said by other (tree shaking, add jsdocs, etc…). Just a quick reminder for the vuejs devs out there we have https://vueuse.org/

Yeah, I figured useHooks was created without knowing about VueUse, but thought they might have become aware of it sense then. It makes sense, because though the code is heading in the direction of VueUse in terms of being maintained and well rounded, the structure of useHooks is quite a bit different. It has the code alongside the Markdown: https://github.com/vueuse/vueuse/tree/main/packages/integrat...

Demo: https://github.com/vueuse/vueuse/blob/main/packages/core/useWebNotification/demo.vue

Also take a look at https://vueuse.org/ which might save you some lines :)

For what it's worth my timeframe is very similar to yours! Started in 2019, no React / Angular. I think looking at great codebases like [VueUse](https://github.com/vueuse/vueuse) shows off the best of composition API.