So the point is to improve SEO of Vue apps
Perhaps useful to some sites. Assuming Google has issues with Vue. Not useful for someone doing content behind a sign-in that isn’t going to ever be SEOed anyway?
Nuxt.js over Vue.js: when should you use it and why
11–20 of 80 posts
Re: Nuxt.js over Vue.js: when should you use it and why
#12My biggest thing with Nuxt is that only the first page load is server side rendered. Everything else is client side. So doing complex search and re-render is done client side.
Re: Nuxt.js over Vue.js: when should you use it and why
#13I admit I don't know the space that well, but I find it interesting that you get static site generators for SPA frameworks, and the companies behind them get really significant VC funding.
Naively it seems a trivial problem, but I guess that SEO for SPA is not as trivial as I imagine?
Re: Nuxt.js over Vue.js: when should you use it and why
#14Earlier quoted context omitted.
probably because there are so many js “frameworks” that they are running out names
Sort of makes me bummed out that the Dart project failed. If there was one time when we could have escaped the client side hell that is JavaScript it would have been then, when chrome had astonishing market share, and Dart could compile down to JS to ease the transition until native support became standardized. But nope, here we are with anotherone.js every week.
what makes you say it failed? Flutter is growing strong.
Re: Nuxt.js over Vue.js: when should you use it and why
#15My biggest thing with Nuxt is that only the first page load is server side rendered. Everything else is client side. So doing complex search and re-render is done client side.
If you use query params, the search and render can be done server side..
Re: Nuxt.js over Vue.js: when should you use it and why
#16Earlier quoted context omitted.
Sort of makes me bummed out that the Dart project failed. If there was one time when we could have escaped the client side hell that is JavaScript it would have been then, when chrome had astonishing market share, and Dart could compile down to JS to ease the transition until native support became standardized. But nope, here we are with anotherone.js every week.
what makes you say it failed? Flutter is growing strong.
Is there a way around the nested mess in Flutter widgets? I took a stab at a small app but it was basically a new div hell. Besides that however, it was quite neat.
Re: Nuxt.js over Vue.js: when should you use it and why
#17Warning that Nuxt.js is almost 100k out of the box, making it unsuitable for mobile usage.
It runs just fine for my site, across browsers and OSes.
Re: Nuxt.js over Vue.js: when should you use it and why
#18My biggest thing with Nuxt is that only the first page load is server side rendered. Everything else is client side. So doing complex search and re-render is done client side.
If you use query params, the search and render can be done server side..
Which should be done because it helps the user very much.
Sharing filtered links or storing filtered links in your favorites becomes impossible when the query parameters don't change.
Re: Nuxt.js over Vue.js: when should you use it and why
#19Re: Nuxt.js over Vue.js: when should you use it and why
#20Warning that Nuxt.js is almost 100k out of the box, making it unsuitable for mobile usage.
In what year, 2004? A single ad can take up that much space.