Publication mise en cache pour en conserver une trace.| larlet.fr
Frameworkism is now the dominant creed of today's frontend discourse, and it's bullshit. We owe it to ourselves and to our users to reject dogma and embrace engineering as a discipline that strives to serve users first and foremost.| Infrequently Noted
JavaScript overindulgence remains an affirmative choice, no matter how hard industry 'thought leaders' gaslight us. Better is possible, but we must want it enough to put users ahead of our own interests.| Infrequently Noted
I have worked with dozens of teams surprised to have found themselves in the JavaScript ditch. They all feel ashamed because they've been led to believe they're the first; that the technology is working fine for other folks. It isn't.| Infrequently Noted
It would be tragic if public sector services adopted the JavaScript-heavy stacks that frontend influencers have popularised. Right?| 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
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
Despite advances in browser tooling, automated evaluation, lab tools, guidance, and runtimes, modern teams struggle to deliver even decent performance with today's popular frameworks. This is not a technical problem per se. It's a management issue, and one that teams can conquer with the right frame of mind and support.| Infrequently Noted
The idea of the browser pre-caching heavily used JS libraries is an attractive nuisance: looks good, probably won't work. Is there a workable version of this idea? What would the constraints on it be? Could it ever be effective and fair? Down the rabbit hole we go.| Infrequently Noted