3 ms·
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
by pjmlp 2y ago
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.
- rxliuli 2y agoI 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.
- CharlieDigital 2y agoThe 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. [0] https://www.youtube.com/watch?v=zvjOT7NHl4Q https://www.youtube.com/watch?v=zvjOT7NHl4Q
- rxliuli 2y agoYes, that's exactly my point. Vue 3 just improves things using existing technologies instead of creating truly fresh solutions.
- CharlieDigital 2y agoWait, 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. [0] https://github.com/stackblitz/alien-signals https://github.com/stackblitz/alien-signals