I just switched fully to Vue / Nuxt after many many years of React and next. While I truly love the JSX used in React and the way how you write components, I had so many headaches over the past years duo to weird behavior which came mostly from hooks. And I don't like the fact that state management is still not as great as in other frameworks. The switch felt so smooth and honestly I'm thinking now why this took me so many years. I heard from friends and colleagues that Vue is great, but never had the motivation for it but oh boy was I stupid. Using nuxt now daily for two months and I hadn't any impediments or so and I'm enjoying it so far.
Thanks 🙏 Sadly it is still not public. Evaluation was done in March this year. Rough results were: * Nuxt has amazing RPS compared to Next/Angular * Next.js has the lowest "hydration cost" due to RSC * Angular wasn't good in either
Vue / Nuxt has been a high performer for so many years and too modest / quiet on this front I feel. Interesting also is ‘# years in pole position’. I feel as one of the first truely Open Source front end libraries, not enough credit is given to the little guy vs Major corps (or the people who have helped them). (I would add, Open Source, as a collective seems to be winning the day).
@@TheAlexLichter I would use it for to trigger any side effects in another part of my application like recalculate stocks when user sets nearby store address but in certain pages. Would love to hear your suggestion and is the $emit with its name available under global nuxt instance??
@@bishal_mishra99try to avoid using too many emits. Pinia or a simple composable with shared state is probably the better way. I also wouldn’t really call it an event bus, as that has a very different meaning in the data science world😉
@@TheAlexLichter I would actually really love a video about Nuxt and styles :) Scoped vs unscoped? Any performance difference? Vanilla styles, vs less/sass/stylus? Importing into a style tag (import, @use etc). Is the content of a style tag always inlined in the end or are we sometimes adding css files that need to be referenced? Do style tags work exactly the same when added to components, pages, layouts or app files? Render blocking issues and performance in general for styles. Style tag vs utility class frameworks?
I like svelte very much, but I don't like the ecosystem. Which makes me quite hesitent to transition to vue. They are similar but vue has bigger ecosystem.
I don't use vue in my current projects, but if Vue is like it was in the past it is better than Svelte because you can compile components and reuse them more easily than Svelte
@@andreilucasgoncalves1416 What do you currently use and why? Honestly, I looked into nuxt a bit, it handles most things much better than sveltekit, which makes me more likely to migrate to nuxt. I espcially like the dev tools, file structure, the auto-imports. All of which are great pain in sveltekit.
I think of Vue and React as "component-level" frameworks while Nuxt and Next are "app-level" frameworks for me. Because you "use" a library, like lodash - but you write code "the framework uses" like in Vue 🤔
Nuxt has far more features than Next.js. Next.js is more popular because it is based on React, which is backed by Facebook, while Nuxt.js is based on Vue, which doesn't have a major company behind it.
What do you think about the results?
What about Angular SSR?
@alexanderkim7241 see the linked PR (and also the mention in the video)
Nuxt has been a pleasure to use at an enterprise level
Really glad to hear that! What did you build with it?
I just switched fully to Vue / Nuxt after many many years of React and next. While I truly love the JSX used in React and the way how you write components, I had so many headaches over the past years duo to weird behavior which came mostly from hooks. And I don't like the fact that state management is still not as great as in other frameworks. The switch felt so smooth and honestly I'm thinking now why this took me so many years. I heard from friends and colleagues that Vue is great, but never had the motivation for it but oh boy was I stupid.
Using nuxt now daily for two months and I hadn't any impediments or so and I'm enjoying it so far.
Nuxt+Vue is love 💚
💯
nuxt is love, nuxt is life
I really enjoy using Vue JS and Nuxt JS in my projects and as a Turkish developer, I follow the developments closely.
🎉🎉
✨
Just so you know … nuxt and vue could’ve been last and I’d still choose them
Me too
When was the evaluation of meta frameworks done (what nuxt version etc.), is the thesis public available? :) But for sure very informational vid.
Thanks 🙏
Sadly it is still not public. Evaluation was done in March this year.
Rough results were:
* Nuxt has amazing RPS compared to Next/Angular
* Next.js has the lowest "hydration cost" due to RSC
* Angular wasn't good in either
Interesting, can you open source the comparison you did between angular, next and nuxt? So that everyone can see the code and improve it.
Yes, as soon as the thesis is published I will!
@@TheAlexLichterNice, great video by the way.
@oussaber thanks 🙏🏻
Vue / Nuxt has been a high performer for so many years and too modest / quiet on this front I feel.
Interesting also is ‘# years in pole position’. I feel as one of the first truely Open Source front end libraries, not enough credit is given to the little guy vs Major corps (or the people who have helped them).
(I would add, Open Source, as a collective seems to be winning the day).
Hey Alex! as always a great video
Thank you ☺️
I personally am not a big fan of the pattern due its shortcomings compared to eg a pinia store or composable.
What would you use it for?
@@TheAlexLichter I would use it for to trigger any side effects in another part of my application like recalculate stocks when user sets nearby store address but in certain pages. Would love to hear your suggestion and is the $emit with its name available under global nuxt instance??
@@bishal_mishra99 I think pinia store should suffice your requirement
@@bishal_mishra99try to avoid using too many emits. Pinia or a simple composable with shared state is probably the better way.
I also wouldn’t really call it an event bus, as that has a very different meaning in the data science world😉
@@gro967 Yes I was just curious 🧐 to see if there's a cleaner way without an extra state. Ooh, what does it mean in the DS world?
Vue es el mejor❤, svelte como siempre con su versión 5 beta en todos las comparativas, su versión estable es la 4
I missed a heartbeat when you said scoped styles are problematic 😱
When I researched and read into it I was also shocked at first 🙈
@@TheAlexLichter I would actually really love a video about Nuxt and styles :)
Scoped vs unscoped? Any performance difference? Vanilla styles, vs less/sass/stylus? Importing into a style tag (import, @use etc). Is the content of a style tag always inlined in the end or are we sometimes adding css files that need to be referenced? Do style tags work exactly the same when added to components, pages, layouts or app files? Render blocking issues and performance in general for styles. Style tag vs utility class frameworks?
@leopoldkristjansson there are 1-2 issues in Nuxt that should be fixed beforehand with regards to that but I agree! Added on the list
amazing, vue is best!
Yes, but there is a nuance)))
There is indeed!
I like svelte very much, but I don't like the ecosystem. Which makes me quite hesitent to transition to vue. They are similar but vue has bigger ecosystem.
Svelte and Vue have quite similar ideas here and here. Definitely give Vue and Nuxt a try! 🔥
I don't use vue in my current projects, but if Vue is like it was in the past it is better than Svelte because you can compile components and reuse them more easily than Svelte
@@andreilucasgoncalves1416 What do you currently use and why?
Honestly, I looked into nuxt a bit, it handles most things much better than sveltekit, which makes me more likely to migrate to nuxt. I espcially like the dev tools, file structure, the auto-imports. All of which are great pain in sveltekit.
Vue and React are libraries not frameworks. Next and Nuxt are actual frameworks. Would like to see comparison between the frameworks.
I think of Vue and React as "component-level" frameworks while Nuxt and Next are "app-level" frameworks for me. Because you "use" a library, like lodash - but you write code "the framework uses" like in Vue 🤔
HTMX is the fastest of them all. :D
Especially when it comes to SSR 🫠
(HTMX can’t do “SSR” the way React, Vue, Svelte etc can)
too much words
Not enough words 👀
(Happy for more detailed feedback!)
Nuxt has far more features than Next.js. Next.js is more popular because it is based on React, which is backed by Facebook, while Nuxt.js is based on Vue, which doesn't have a major company behind it.