Why you SHOULDN'T use Vue 3 Reactivity Transform!

#vuejs #vuejs

In a previous video I discussed reactivity transform and use $, and $ref. In this video I discuss an update to it, and some comments I got from the last video!

👉Check out my last video on Reactivity Transform in depth!

👉 Sign up and get free Vue cheat sheets and updates!

👉 Need some help with a project, level up your skills, Vuetify or Nuxt bug? Check out my 1-on-1 mentoring!'

Follow me!

[codedjango]

I like the Vue3 <script setup> of the composition API because it just makes the code very simple and easy to read.

[kylebruns]

I like that Vue is independent and listens to its community.
I dislike that Vue has a smaller community than React. I really hope this changes!

[ismaeljalbuna]

I love the SFC.. it makes the code easier to read, full TS support, volar extension... as well as vite which is way faster than other tools

[JohnPombo]

The thing I love most about vue are the cohesive ecosystems it creates. For example create-vue is such a great cli tool that prompts you for options before setting up your project with minimal boiler plate. The thing I dislike most about vue is the lack of opportunities available out there for jobs. My wife is looking for a career change and I got her hooked on vue. But now she is looking for a job - and having to learn react on the side because that is where the demand is.

[salvaje]

If there's one thing I like about Vue is how easy it is to get into. It feels like working with vanilla js html and css but with some syntactic sugar

[brandonleichty]

Like: Single File Components (SFCs). One of the biggest things I love about SFCs is that I don’t have to decide between using Styled Components, CSS Modules, or any of the hundreds of other ways to write CSS in other frameworks.

Dislike: The size of the Vue ecosystem. Vite, Vitest, and Pinia are absolutely amazing. But once you need a package outside of the core Vue packages, the options tend to be quite limited.

[cornshed]

I feel .value should have been unwrapped by default, and the ref should've had .ref instead for times when we need to pass the ref
I like reactivity transform, especially for computed, but its just bringing a lot of mental overhead when working in composables, I can't get my head around $$() syntax
I hope they go in that direction for Vue 4, although the migration could get messy

[OnceNobody]

Thank you for the update video. I started to work with Vue after many years with Angular. What I like about it, is the ease of learn and how fast you get to do productive work. What I don't like is how sometime the magic of Vue gets confusing. For example when components are magically there without me importing them. Also joined in the transition to the Vue3 and it is hard to distinguish if the solution online is for Vue3 or previous versions.

[Nekoeye]

Vue 3 <script setup> is awesome. Period.

[broscore]

I like about vue the composition api and the overall struture of .vue files. Also love the community based aspect of the framework. There is not really a thing I dislike about vue thats why I choose it over react or angular :P

[siyedyoussef]

Keep the fitness journey you look very fit 💪💪💪

[eyalbarta]

I'm in the process of migrating some complex components from vue2 to vue3 composition API...
My 2 major pains with the <script setup> syntax is
- the need to chain .value to every reactive variable and computed.
- No syntactic sugar for mapGetters mapState from store.

So I have an array of several state vars and getters from store, now I need to have a line of code for each one.. not very minimal :(
plus now in all my related methods, I need to chain .value to every single variable... that sucks.

I was really excited when I found reactivity transform because it saves the need to .value everything, which is IMO significant for massive blocks of code... what I don't understand, for such a time saving feature, why is it considered confusing and experimental? it's function seems pretty straight forward, simple and most of wall NEEDED..

Erik, when you spoke with Evan, did you get any idea from him when this feature will be production ready..? I would totally opt-in right now, but hearing from the founder this should not be used in production is keeping me from doing that... Obviously I want this in production :)
Also, any thoughts about my other pain (mapping from store)?

Thanks for your vids and I'll appreciate a response :)

[Ivan-qpyd]

Yes sure I agree It is an experimental feature and no one should use it in real project but we cannot avoid human behaviour when someone can decide to write a "modern code" It would be better install an extra package for using this feature instead of having it in vue library. And other problem in Vue3 is Composition and Option API (2 similar frameworks in one) if you started to learn vue js You would learn both of them but unfortunately many low level developers don't care about it and learn only new features but in real project they can see absolutely different syntax. In this case if one company is looking for some developer on front-end position must clarify what type of api the candidate must know because it also impacts on logic and test in a project

[RiadDZz]

i like the composition api of vue, it really is a game changer, also the script setup

[mihaiudvar]

Well, the only thing I dislike so far is that there's no that many users of Vue hence not as many examples to get inspiration from or to solve bugs.

[shonya]

Vue is love, Vue is life. Volar is great. Live long Vue!

[VELIXYZ]

Thank you for the video!

I like about VUE everything.
Composition API, easy to learn and use, community, youtube channels!

[AdroSlice]

This feature got deprecated, or rather just didn't make it. I'm really sad about that, because the existence of reactivity transform is what pushed me from the verbose options API with its unstable "this" to the much cleaner, much better at feature grouping composition API with <script setup>. Now that I can't really justify bringing it to a project anymore, as it's now an independent (and worse implemented) plugin, it's honestly killed a lot of my enthusiasm for vue and frontend in general. The next time I start a project, it's probably gonna be in svelte, solid, or some other fancy new thing.

[KirkWaiblinger]

Thanks for your response to my comment!

[todpale]

Thank you very much for such detailed feedback! "Mom, I'm on TV!" :D