westbrookGoing fast probably isn't good for anyone. Absolutely none of your stakeholders benefit more than getting to prime the work queue again sooner. Quality. Quantity. Focus. Pleasure. All that starts to leak through the cracks that silently grow in parallel with your "velocity".
Ben Delarre
@bendelarre
- 381 Followers
- 374 Following
- 1.4K Posts
Wrangler of web app technology. Maker of things both physical and digital.
Of course when I start that project I'll no doubt order another batch of something else I get wrong and thus perpetuate a never ending chain of constraint driven project invention.
My inability to read AliExpress product listings carefully enough to order the right things the first time contributes to the excessive collection of random components I hoard.
I now have 200x 27mm piezo discs I need to invent a new project for.
Open Web AdvocacyFirefox now supports Web Serial on desktop 🦊
This means web apps can connect to compatible hardware devices such as microcontrollers, development boards, 3D printers, power meters, and other serial-connected hardware.
Allowing the Web to do even more!
📖Read more:
https://blog.mozilla.org/en/firefox/firefox-web-serial-adafruit/
🧵👇️ (1/11)
Alex RussellA point excerpted from a talk I gave earlier this week at Microsoft's internal performance symposium (alt talk title: "CSS-in-JS: Frontend's Worst Idea"):
Browsers are virtual machines tuned to efficiently turn *markup* into *pixels*.
If your system tries to generate pixels from not-markup, you'll be working against the grain of the system, and should expect to suffer massive performance penalties -- both in CPU and memory use -- as a result.
For deep reasons, this is not going to change.
Watching teams start migrations towards React "because our team knows it, and we want to have LLMs generate it" is so depressing.
Sure, shoot yourselves in both feet while you're at it.
Large Heydon ColliderPlain language guide to JavaScript performance:
* Don't do a lot
* Don't do something multiple times that only needs doing once
* Don't save things you later won't need
* Aim for fast code, not neat or terse code
* NEW: Don't download it if you're not going to use it
* NEW: Don't do it with JS if CSS or the browser can do it instead
* NEW: Don't do in the browser what can be done on the server
Edit: thanks for the suggestions!
That's all I can think of.
🔥 "Capable browsers, and the PWAs they support, hold the power to grow an ecosystem of applications that no gatekeeper can own or tax, based on standardised APIs that resist enclosure. But few outlets are connecting these dots for readers."
📖 Read: https://infrequently.org/2026/04/the-web-is-an-antitrust-wedge/
The Web Is An Antitrust Wedge
Armed with new powers to rein in the worst excesses of mobile's duopolists, regulators around the world are struggling to find their footing. The UK's CMA is only the latest to pose capitulation as success. Far from unlocking growth and dynamism, regulatory timidity is reducing enforcers' future room for manoeuvre and hampering home-grown competitors to Big Tech. Unleashing the web would fix a great deal of what's broken, but regulators are falling down on the job. It's time we spoke plainly about it.
Stephanie EcklesI’m excited to share a new project from Adobe Spectrum Web Eng that tracks support for #CSS features within and across the shadow DOM. Think “CanIUse” but for CSS for web components.
The goal is to surface how modern CSS behaves when light and shadow DOM contexts meet, providing visibility into feature parity, usage details, and outstanding issues and bugs. We hope it’s a useful resource for the web components community, and we’d love your feedback and contributions!
Recruiter messaging me about a job opportunity.
What's this? An interesting job building web apps for high performance monitoring of generalized novel hardware systems... Right up my street. Hardware, check, web, check, visualizations, yup, performance, yes please!
Oh... "3+ years experience with React and CSS-in-JS". Ah.
You didn't actually mean you were serious about performance did you?
I do not, nor would I ever, recommend you try and build high performance web apps with React. Bye!