4 ms·

It's funny how such snooty nose-in-the-air attitude about boutique hand written js masquerades as a choice any company can make. So, we can only hire artisans

It's funny how such snooty nose-in-the-air attitude about boutique hand written js masquerades as a choice any company can make. So, we can only hire artisans who hand tailor every event handler, who writes bespoke careful updates that never conflict and always handle every corner case of the dom right? And you and your 63 clones that NYT has hired will all work in harmony & concordance doing your bespoke vanillajs practices. Reacts vdom is pretty sweet. Even the old iterations of React can go eliminate a lot of paints. Old websites used to have plenty of write-read-write loops that internally block the dom, that react's lifecycle generally helps guard against. The article here talks about even further improved batch updating that React 18 can help with. Apologies my attitude, but it's just remarkably how much rancis ass attitude there is about React & how fucking stupid it sounds. I know it's the internet, that people will forever be springing up to spout off, but it's so sad having such miserable negativity hounding such perfectly respectable tech.

w-ll 2y ago
Lol, you hear yourself right now. NYT site is fast, but is broke as hell. Even turning off uBlock it downloads 10mb of assets before the fold and still doesn't work. This is more salt of the earth reality, maybe you're projecting the snooty nose-in-the-air boutique'ness of React.
- mason_mpls 2y ago
  I’ve never had and noticeable issues using NYT and I’ve been subscribed for over a year, not sure what you’re talking about here
- jauntywundrkind 2y ago
  React is as plebeian as it gets, is the mass-adopted industrial tooling. It's a rote boring and commonplace way of doing software. I generally agree that most sites are pretty bad, are way too big & usually with poor data-architectures (over fetching, re fetching, poor or no data caching). Data storage is notably something React nor very few other things have tried to tackle. GraphQL made a forray & for a while seemed ascendant but it's moment seems to be passing. The core issue of client-server model is still pretty informally handled. But even that has nothing to do with the very obvious & bad issue, that many sites are loaded with obnoxious & heavyweight & surveiling ad payloads. But it's unclear to me again what React has to do with this. (Especially as few of these as systems use React.)

w-ll 2y ago

Lol, you hear yourself right now. NYT site is fast, but is broke as hell. Even turning off uBlock it downloads 10mb of assets before the fold and still doesn't work. This is more salt of the earth reality, maybe you're projecting the snooty nose-in-the-air boutique'ness of React.

mason_mpls 2y ago
I’ve never had and noticeable issues using NYT and I’ve been subscribed for over a year, not sure what you’re talking about here
jauntywundrkind 2y ago
React is as plebeian as it gets, is the mass-adopted industrial tooling. It's a rote boring and commonplace way of doing software. I generally agree that most sites are pretty bad, are way too big & usually with poor data-architectures (over fetching, re fetching, poor or no data caching). Data storage is notably something React nor very few other things have tried to tackle. GraphQL made a forray & for a while seemed ascendant but it's moment seems to be passing. The core issue of client-server model is still pretty informally handled. But even that has nothing to do with the very obvious & bad issue, that many sites are loaded with obnoxious & heavyweight & surveiling ad payloads. But it's unclear to me again what React has to do with this. (Especially as few of these as systems use React.)