Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Like many others, I wasn't a huge fan of the composition API. Felt like we were giving up many quality of life features in the name of a weird "must be like react" push.

On the other hand, once I started actually using it, I found myself liking <script setup> very much. I also like the "ref" thing because I have been pushing for this approach for a long time. Values are objects/proxies is a wasteful, yet powerful approach.

I am not going back to writing Vue 2 style components and encourage all of my co-workers 5o do the same. They are slowly but surely coming to accept it. No more lazy hacks for them



I've had the same experience. The TypeScript support, explicitly defined reactivity so you have fine-grained control yet still simple and understandable code using the same models of computed, ref, and watch etc which anyone can grasp in no time.

I know the churn in the Vue ecosystem is attracting a lot of resentment but I'm absolutely loving it. The Composition API is clean and effective and <script setup> takes it further to svelte-like succincity, Pinia builds on simple reactive state instead of the needless complexity of Vuex, Vite is fast, Volar finally brings type checking to templates and VueUse offers hooks for several little niceties that just make the experience more pleasant (https://vueuse.org/). The only thing I dislike is the macro based reactivity transform proposal which would auto add .value to special refs during the compile step, but that isn't even finalised yet and of course completely optional.

It's a great time to be a Vue dev and I hope they continue developing 3 because even if it's not the same library it was, what we have now is too good to lose and I love using it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: