Perhaps surprising: I agree with @slightlylate that the discussion we're having about web performance isn't helping us move forward as a community.
-
-
Also, I don't "blame" React. Instead I note the probability (approaching 1) that sites with 400K of 1P JS include a relatively heavy framework, too many polyfills, and many other unneeded elements. Heavy FW use is a symptom of broken culture and management priorities.
-
Do you agree that tooling could eliminate or defer enough unused code (in combination with better patterns and programming models) so that the size of the "raw" framework matters less than how many features of the framework you're leaning on?
-
I think tooling -- coupled to good choices in view, routing, and data layers -- is *already* getting real apps to a much better place. Teams need structure. It's why I recommend Polymer Starter Kit and Ionic PWA Starter Kit and Preact CLI and Next.js -- never "raw" view layers
-
I’d strike Polymer from that list given the lack of an SSR story. Fatal to good FMP.
-
That's an...interesting...claim. I see lots of SSR solutions that don't early flush, delay TTFB by a huge amount, double-or-triple-up overall data sent, etc. It's very much a footrace, but if you're lighter you don't need as much force.
-
Just because you can get SSR wrong doesn’t mean you should bet on a technology that won’t ever let you get it right. H2 and SW have similar footguns; I wouldn’t use a framework that prevented me from using them.
-
Show me the traces. It's easy: https://www.webpagetest.org/easy Paste in the URL of a good example, select "Mobile - Regular 3G", hit submit, share WPT result!
-
What evidence would be persuasive to you? Any SSR app being faster than any Polymer app at FMP? Seems like there will be confounding factors.
- 30 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.