3 ms·

To save you a click: apparently https://www.mcmaster.com/ https://www.mcmaster.com/ is very fast. A person who worked there chimes in https://x.com/mattwensing

by yread 2y ago

To save you a click: apparently https://www.mcmaster.com/ https://www.mcmaster.com/ is very fast. A person who worked there chimes in https://x.com/mattwensing/status/1847277743228002635 https://x.com/mattwensing/status/1847277743228002635 saying they focused on speed (competing with paper catalogue), used VB.net and SQL Server with stored procs. Some other guy explains https://x.com/wesbos/status/1847047872770199647 https://x.com/wesbos/status/1847047872770199647 : · Agressive pre-loading pages on hover · fixed image dimensions - there is no layout shift when they load · Dependency Injection (huh?) - only loading the JS needed on the pages where its needed · Uses pushstate to change pages so it feels faster than a full reload · agressive CDN and browser caching · Server rendered HTML (ASP .net) Funny enough they load almost a meg of JS (YUI and jQuery) but you dont notice because it feels so snappy He made a video explaining it: https://www.youtube.com/watch?v=-Ln-8QM8KhQ https://www.youtube.com/watch?v=-Ln-8QM8KhQ which is a lot more interesting than the inane tweet. Maybe we could replace the link with the video?

bigfatkitten 2y ago
> Server rendered HTML (ASP .net) Who could've imagined that some React monstrosity that makes 300 API calls to build each page locally isn't the best way of doing things?
legitster 2y ago
The best part of these methods is that the site would work nearly just as fast on a freaking PDA from the 15 years ago. This is the direction the web was heading before React took over everything.
- caseyy 2y ago
  That's true, we really lost that. Every page would load like static one. Now pages not only take 3-20 seconds to build locally, but there are necessary cookie banner interactions and calls to action (Substack, Medium) that you need to dismiss before you even see the content.
  - bigfatkitten 2y ago
    Or they're like m.facebook.com, and just don't load properly at all. You'd think that with what Meta pays, they could afford to hire someone who knows how to build a web app.

by yread 2y ago

bigfatkitten 2y ago

> Server rendered HTML (ASP .net) Who could've imagined that some React monstrosity that makes 300 API calls to build each page locally isn't the best way of doing things?

legitster 2y ago

The best part of these methods is that the site would work nearly just as fast on a freaking PDA from the 15 years ago. This is the direction the web was heading before React took over everything.

caseyy 2y ago
That's true, we really lost that. Every page would load like static one. Now pages not only take 3-20 seconds to build locally, but there are necessary cookie banner interactions and calls to action (Substack, Medium) that you need to dismiss before you even see the content.
- bigfatkitten 2y ago
  Or they're like m.facebook.com, and just don't load properly at all. You'd think that with what Meta pays, they could afford to hire someone who knows how to build a web app.