Event JSON
{
"id": "d1d48c1e2abfec902e9da9335a292870857d282333635293c23c890ab9a35611",
"pubkey": "0a6a259cdd6b1549c96091aa012f0552bdc4a36f2585efffe059eeb235391ddc",
"created_at": 1719008179,
"kind": 1,
"tags": [
[
"e",
"58ecbf3fa622baf6e2065f8b646f27f2daf4fdb9db05c7fc026be92384e61985",
"",
"reply"
],
[
"e",
"b38270ab8dca4d1bf9c0fc0d715f720f8497e4a3862b74a909ed5bcf83274165",
"",
"root"
],
[
"proxy",
"https://toot.cafe/@slightlyoff/112656920041897216",
"web"
],
[
"p",
"0a6a259cdd6b1549c96091aa012f0552bdc4a36f2585efffe059eeb235391ddc"
],
[
"proxy",
"https://toot.cafe/users/slightlyoff/statuses/112656920041897216",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://toot.cafe/users/slightlyoff/statuses/112656920041897216",
"pink.momostr"
]
],
"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": "340747b6d388d60e92bfc3ecc43c154836e661ea7be2eb21ee00bd94485162f0873282e4a6397912e0a13771e47b8ba9ecbb2d8229de4ea40b49d46b69328084"
}