71–80 of 80 posts
Earlier quoted context omitted.
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.
There are people over on reddit who say that EVERY project should use nuxt. from the lowly todo app, to huge erp projects... Yet, especially for ERP projects, most of those features are problematic. Like SEO. I don't want a search engine to ever see my content. In fact, my robots.txt says not to index it. SSR is a non starter, since everything would vary based on the user, we're just shifting the rendering back to th…
Earlier quoted context omitted.
I'm trying to imagine what browser is so outdated that it struggles to parse 100kb of javascript
It's not the browser, it's the processor that's in most non-iPhones.
Earlier quoted context omitted.
It runs just fine for my site, across browsers and OSes.
You're probably getting down-ranked by Google, they use performance as a metric.
My 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.
I 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?
Imagine you build an e-commerce website that has ten thousands of products, that can be accessed by example.com/products/{product-slug}. Now what is making more sense: 1. Generating ten thousands of .html file for each products in the DB 2. Use routing in Nuxt like this "/products/$productSlug" and query for $productSlug in the database
To me the (2) approach is a clear winner here. And the performance only depends on how fast your API can query a single product from the database, which is pretty fast 99% of the time.
1. Nuxt can runs in SPA mode just like using Vue CLI. The opposite is not true
2. SEO is the winning feature of Nuxt, no doubt.
3. Real server status code: especially useful for redirections and 404 pages. For example if you do `curl -I /some-page-that-does-not-exist`, you will get back 404 status code, which is critical for sitemaps and uptime tools. (Instead in SPA you always get 200 for all the pages).
4. Pages written in Nuxt seems to display faster, because the HTML is sent immediately. I say "display" here, not necessarily "load" faster.
5. Real Express middleware helps a lot when doing route validations and authorizations. You can also make calls to private API without exposing them on the client side.
6. Can adjust the amount of HTML sent to client by wrapping client-side-only components in a component. Which means that on the server you don't need to generate giant HTML for a simple datepicker, and let the browser does that
Earlier quoted context omitted.
My understanding was that it just added to the existing generated list, I can’t work out how you’d tell it to ignore all your current pages and then manually write them all out?
you can use router-module if you want to do everything yourself ( https://github.com/nuxt-community/router-module )
Earlier quoted context omitted.
You're probably getting down-ranked by Google, they use performance as a metric.
And what is the best solution? Client Side Rendering is worse, because users see a blank page until the script is parsed. 100KB is actually desirable, because it's included Vue and Vuex out of the box.
The solution is to have a performance budget at the start of your project so things never get so bad.