I guess 0.0051 is okish for a late night attempt. Great app π
I guess 0.0051 is okish for a late night attempt. Great app π
Not a real app if thereβs no VDOM
Inside out
Two graphs, the first one being "Preact.js downloads over time" 2015-2025, the other being "UFO sightings over time" 1940-2015, showing a vaguely similar increasing trend over time.
OPEN YOU'RE EYES ποΈπποΈ
A GitHub-style pull request merge confirmation. It adds a tipping interface with options (15%, 20%, 25%) and a "Custom Tip" button, plus a "No thanks, just merge" option, turning the merge action into a tip jar moment.
oh what the hell
I hope you donβt suggest: ditch web components for react
Something, something, AI
Another API proposal from TPAC: CSS routes and navigation queries, meaning less JavaScript is needed for view transitions!
https://drafts.csswg.org/css-navigation-1/
https://github.com/w3c/csswg-drafts/issues/8685#issue-1653949919
These two cats are also siblings but that doesnβt really matter πΉ
How broken is today's frontend culture?
A friend points out that the median *mobile* page is now larger than a copy of DOOM (2.6 MiB vs. 2.48 MiB), the 75th percentile page is more than 2 DOOMs, and the P90 mobile page is 4.5x the size of DOOM:
httparchive.org/reports/page...
Chrome DevTools showing that Temporal.Now does work, and that other properties are also available.
Temporal you ask? In all browsers you ask?
Well, I'm told it's coming to Chrome/Edge 144. So, like, very very soon (as in, January).
It's already in Firefox. And being implemented in Safari too.
Screenshot from https://httparchive.org/reports/techreport/tech?tech=ALL,Next.js,Ruby+on+Rails,Astro,SvelteKit,Svelte,React,VitePress&geo=ALL&rank=ALL&page=1
According to HTTP Archive, Next.js sites see the **worst** Core Web Vitals performance when compared to other popular frameworks
httparchive.org/reports/tech...
Is Heximal csp complian?
New release: <is-land> v5.0.0
ποΈ Better performance
β°οΈ Adds *more* browser support
πͺ Passive event listeners with `on:interaction`
βοΈ Rename tag name or on:* attributes
π Framework APIs
github.com/11ty/is-land...
This is excellent. ππΌ
βOpen source, the thing that drives the world, the thing Harvard says has an economic value of $8.8 trillion.
Most of it is one person.
And I can promise you not one of those single person projects have the amount of resources they needβ
opensourcesecurity.io/2025/08-oss-...
This is some of the hardest shit I've seen in my life
Just kill it
Ermh, could we have a sneak peak of that code?
Does it work also for `size: stretch;`?
Family owned printersβ¦
This is gold
Ok, here's my second post on a potential native DOM templating API, diving into exactly what such an API should actually look like and why.
justinfagnani.com/2025/06/30/w...
Scroll driven animations is another one
Okay gang, those who sling HTML, CSS, JS, which _Firefox_ bugs are blocking you? Which features do you think need improving? What new features would you like to see? What work would you prioritise? Big or small, bonus points for linking to a bug (even more for filing bugs then linking them)!
ReAcT π
Also will prefers-color-scheme css work in a favicon?
Yay
Things escalate too fast these days, vibe coding to vibe debt within weeks π
π Coming to Chrome DevTools in Chrome 138: CSS Value Tracing
When you hover a --custom-prop in a `var()`, DevTools currently shows you the computed value. From Chrome 138 onwards, you can hover the `var` part to see how CSS actually got to that value.