Scott Jehl on Nostr: It’s strange that the most egregious performance anti-patterns in frontend dev just ...
It’s strange that the most egregious performance anti-patterns in frontend dev just persist, seemingly unlike other outdated practices. Like, putting JavaScript in the way of content delivery is a fundamentally bad pattern. Maybe the worst common issue. We all know this. But it’s still popularly practiced! It’s weird that we’re still advising the same things about performance from 2012. We managed to flip all of our Ajax to fetch() pretty quickly; why not these practices that impact users more?
Published at
2024-01-30 20:02:00Event JSON
{
"id": "650408741e1369a33276c7cc1cf314a41fadcf54663b5c4e572031dccbe57ffa",
"pubkey": "b366513fe344d7bcd092cb92e8dbb8f07ef6321dbdf1a05fd3439b0ba381c150",
"created_at": 1706644920,
"kind": 1,
"tags": [
[
"proxy",
"https://mstdn.social/users/scottjehl/statuses/111846681527089425",
"activitypub"
]
],
"content": "It’s strange that the most egregious performance anti-patterns in frontend dev just persist, seemingly unlike other outdated practices. Like, putting JavaScript in the way of content delivery is a fundamentally bad pattern. Maybe the worst common issue. We all know this. But it’s still popularly practiced! It’s weird that we’re still advising the same things about performance from 2012. We managed to flip all of our Ajax to fetch() pretty quickly; why not these practices that impact users more?",
"sig": "5f0b1fec51f29d59da255faede38042dfb2981d99ac36ded2d97416ef9132c065e57b9a6e912839f96e26c1d2ce94963214e1a7eb55c6207694ff20d3d0ffa69"
}
