My use of Next.js is due to SaaS products that only support Next.js on their first party support and teams I work with, thus I won't be using Vue, regardless of how great it happens to be.
Privately I seldom use any kind of JavaScript frameworks, other than when doing WebGL/WebGPU side projects, and then it is mostly Babylonjs.
I think Vue 3 is better than Svelte 5's runes, but unfortunately, in my 7 years of using Vue, I've realized that Vue is just a follower of React and may never catch up, as it is only trying to optimize the status quo rather than break the deadlock.
Re:Svelte5: A Less Favorable Vue3
by CharlieDigital on Saturday March 08, 2025 @12:45PM
(#43301914)
The exact opposite is probably true at a technical level.
Vue 3.6, for example, is incorporating a new signals rebuild that's several times faster and probably the fastest signals implementation out there[0]
Vue Vapor will also release in experimental mode in 3.6 and once it's mainstreamed, will probably also be among the fastest render models.
Both changes do not affect the DX and require no migrations, but will provide faster performance for ever more complex apps.
Yes, that's exactly my point. Vue 3 just improves things using existing technologies instead of creating truly fresh solutions.
Re:Svelte5: A Less Favorable Vue3
by CharlieDigital on Saturday March 08, 2025 @04:23PM
(#43303661)
Wait, wait: so your take is that the upcoming alien-signals[0] library integration -- created from scratch to improve Vue's signals performance -- is just "using existing technologies instead of creating truly fresh solutions"?
Basically, if I understand correctly, it's not "shiny" enough -- even though it is going to significantly improve signals performance.
I am also an old timer. Hand rolled HTML and JavaScript since '97?
Came up with ASP (both VBScript and JSCript (it's like we're full circle with JS SSR)). Move to ASP.NET when it was in beta. jQuery, Prototype, Knockout.js.
Vue.js SFC is the thing that feels closest to HTML + JavaScript components done right. It's reactivity model is the same as that of JS whereas React's reactivity model is "inverted" [0]
The state model (Pinia or just composable reactive primitives) is simple, Just Works, and never gets in your way.
Lots of folks like JSX because they don't like HTML and CSS. I'm the opposite; I like Vue because I like HTML and CSS and I like JavaScript. Vue is HTML + JavaScript done right with a congruent reactivity model.
[0] https://chrlschn.dev/blog/2025/01/the-inverted-reactivity-mo...