Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue.js 3

github.com

Post reply on HN
Print view View original

31–40 of 308 posts

Re: Vue.js 3

#31

Post by ausjke »

Good to see this out. I want to pick a good frontend scheme for future projects but I don't really need most of the fancy SPAs and the complexity coming with it.

Invested a few weeks on Vue a few months back, then the concern about 'React has 80% market share and you can find React developer much more easily in the west" never went away.

Maybe Mithril is the way out? I just need a really light-weight client-side-ajax MVC for some embedded product webUI, in fact jquery+BT might do the job well but again, jQuery is not modern any more.

Not a frontend guy, picking a direction there has always been challenging.

Re: Vue.js 3

#33

Post by paulsmal »

JMTQp8lwXL wrote: post #18
fyrmio wrote: post #6

> Vue 3 has demonstrated significant performance improvements over Vue 2 in terms of bundle size (up to 41% lighter with tree-shaking), initial render (up to 55% faster), updates (up to 133% faster), and memory usage (up to 120% less). What does 120% less memory usage mean, really?

I can only suppose it means 100% less memory consumption by Vue, and then Vue somehow frees 20% of memory from other running processes, which would lead to some pretty interesting results.

also being 130% faster it's rendering results before computations

Re: Vue.js 3

#34

Post by gorbypark »

jaequery wrote: post #28

if this means no more Vuex, i'm all for that. that extra abstraction layer never proved useful to me.

Vuex is still around. They just haven't finished integrating it into Vue Dev Tools, yet.

Re: Vue.js 3

#35

Post by ahpearce »

ausjke wrote: post #31

Good to see this out. I want to pick a good frontend scheme for future projects but I don't really need most of the fancy SPAs and the complexity coming with it. Invested a few weeks on Vue a few months back, then the concern about 'React has 80% market share and you can find React developer much more easily in the west" never went away. Maybe Mithril is the way out? I just need a really light-weight client-side-ajax…

AlpineJS? A bit polarizing, but definitely lightweight...

Re: Vue.js 3

#36

Post by lloydatkinson »

gavinray wrote: post #26

My only wish now is for the TSX experience to be rounded out. From a reactivity standpoint, Vue has a much more ergonomic/easy to use API for handling component state, effects, and computed values (in my opinion) than React. But in the last 6-8 months, I've leaned away from Single-File Components because when you want to do something like define a bunch of small components, it's a lot more difficult to do than with m…

They have improved TSX support in Vue 3. Did you try it? What does or does not work? I'm planning on switching to TSX.

Re: Vue.js 3

#37

Post by Exuma »

I just started vue 3 and its incredible compared to my experience with react. Way to go Vue team!!!

Re: Vue.js 3

#38

Post by TekMol »

I still don't see a reason why one would use Vue or React.

I agree that templating of data is something you should use a library for. But there are great templating libraries. Handlebars for example.

Can someone give a short example of code that would be more elegant using Vue then just a simple template engine?

Re: Vue.js 3

#39

Post by Exuma »

diminish wrote: post #24
lykahb wrote: post #4

I am impressed how they redesigned both internal architecture and a public API while keeping the users happy. Many well written projects fall into the trap of being a great fit for the contemporary practices but become less relevant over time as the ecosystem changes. Well done, Vue!

curious how easy it will be to move from vue 2 to vue 3

Its very easy for users, quite difficult for library maintainers

Re: Vue.js 3

#40

Post by gavinray »

jaequery wrote: post #32

is reactive() just a mere wrapper around ref() ?

Kind of -- reactive() lets you declare multiple values at once, and you can read the property directly.

ref() is for single values, and to get at the actual VALUE, you need to use "myRef.value"

   const state = reactive({ msg: "hello", count: 1 })
   state.msg // "hello"
   
   const msg = ref("hello")
   msg.value // "hello"
Though when you use ref()'s in templates, it will bind to .value for you.
Post reply on HN