The Performance Inequality Gap, 2024 - Infrequently Noted
How much HTML, CSS, and JavaScript can we afford? More than in years past, but much less than frontend developers are burdening users with.| Infrequently Noted
Publication mise en cache pour en conserver une trace.| larlet.fr
How much HTML, CSS, and JavaScript can we afford? More than in years past, but much less than frontend developers are burdening users with.| Infrequently Noted
New web services are being built to a self-defeatingly low UX and performance standard, and existing experiences are now pervasively re-developed on unspeakably slow, JS-taxed stacks. At a business level, this is a disaster, raising the question: why are new teams buying into stacks that have failed so often before?| Infrequently Noted
To serve users at the global P75 of devices and networks, we can now afford ~150KiB of HTML/CSS/fonts and ~300-350KiB of JavaScript (gzipped). This is a slight upgrade on last year's budgets, thanks to device and network improvements. Meanwhile, web developers continue to send more script than is reasonable for 80+% of the world's users, widening the gap between the haves and the have-nots. This is an ethical crisis for frontend. Meanwhile, the most popular tools and frameworks remain in stub...| Infrequently Noted
Some folks claim that Apple's mandated inadequacy for browsers and their engines is somehow beneficial to the cause of ensuring a diverse pool of web engines. Nothing could be farther from the truth, but to understand why, we need to understand how browsers are funded. With that understanding, we can see that not only has Apple has starved its own browser team of resources, but has done grevious damage to Mozilla along the way.| Infrequently Noted
