Alex Russell on Nostr: Processing JS, e.g., is at least 3x more expensive per byte than HTML and CSS. That ...
Processing JS, e.g., is at least 3x more expensive per byte than HTML and CSS. That means that you can afford three times as much declarative content given a constant latency budget. Including network time, the multiple might drop to only 1.5-2x, but holy cow! In a world awash is shockingly slow Androids and low-end Windows machines, JS is (and always has been) special-occasion food.
Published at
2024-06-21 22:16:19Event JSON
{
"id": "7bde41f0f4d61a47ea99eb214bf7197b483c064555594441c34d1fe7843c1cbb",
"pubkey": "9a9958954da280d9b92d48aa4e7cb0481d4e71c54694cad1d090cea273f5a919",
"created_at": 1719008179,
"kind": 1,
"tags": [
[
"e",
"7566a185b372703e510827014d192c3dabe6b37a9f0b3095ca4b775cb87fcc96",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://toot.cafe/users/slightlyoff/statuses/112656920041897216",
"activitypub"
]
],
"content": "Processing JS, e.g., is at least 3x more expensive per byte than HTML and CSS. That means that you can afford three times as much declarative content given a constant latency budget. Including network time, the multiple might drop to only 1.5-2x, but holy cow! In a world awash is shockingly slow Androids and low-end Windows machines, JS is (and always has been) special-occasion food.",
"sig": "f73acdbfec96ce1e69f60a52a776b6277288a91bc37765af7c521dd007c8e19bdb8903d5fca6c6c27b47c0b535c5455340ec4154c93017216cc50e71aebe3130"
}
