 It is *intense* just how badly the JS/React brainworms have infected the frontend community. Every single NYT story page has *both* a 437KiB (1.5MiB unzipped) *and* a 474KiB (1.7MiB) JS file, to display ~50K of text. It isn't ad bloat. It isn't tracking. It's this sort of bunk: 6 comments
@slightlyoff careful the old powers of imagemaps should not be trifled with. The web ancients speak of these horrors and other unspeakable things like SPAs done with framesets or unnatural tags like <layer>. We must tread lightly over the web tech burial grounds. 🤣  @slightlyoff My fucking god making their website with Unity3D would lead to performance improvement @slightlyoff I can't believe someone with your background and expertise comes out with this kind of reactionary crap. No doubt it can be optimised, but you know full well they are not just "showing 50k of text" are they? Besides implementing a design system and branding (which may not be important to you but it is to them), they are also taking care of logging in, and general basic functionality, a/b testing, maybe some of those lovely interactive stories of theirs, etc @gotofritz You say all this like there's is no alternative to doing it the most expensive way possible. As though the NYT online was not a thing before the invention of React/CSS-in-JS/etc. Lead-plated vs. nothing is a false choice. |
Gregory's Server
An image map would be faster.