Sympa la démo et le code !

Si vous avez joué sur Mac dans les années 80 et 90, vous ne connaissez peut-être pas Rebecca Heineman, mais vous avez probablement profité de son travail. La développeuse, qui est décédée le 17 novembre 2025 d'un cancer, était en effet spécialisée dans les jeux vidéo et notamment dans les portages sur les plateformes Apple.

TL;DR: You stop learning.

No single measure can eliminate supply chain risk. But choosing fewer dependencies, shallow graphs, exact version pins, no postinstall, and a slow, review-heavy upgrade cadence together make Obsidian much less likely to be impacted, and give us a long window to detect problems before code reaches users.

Dohmke will remain through the end of 2025 to oversee the handover, and Microsoft will likely move incrementally to avoid disrupting GitHub’s user base. But the long-term trajectory is clear: GitHub is now an AI-first product group inside Microsoft, and its success will be measured as much by the adoption of Copilot and related tools as by the health of its broader developer ecosystem.

For developers, this is a fork in the road. Will you adapt to a platform whose incentives are increasingly tied to a single vendor’s AI strategy? Or will you take your git and ball and go elsewhere?

Most of our software has been shaped by chance decisions made in haste by people who could not have predicted how the system would end up being used today. Some chance decisions become structural problems. They constrain the system, make it inefficient, hacky, slow.

There was also, notably, a sense of typically stoic acceptance across everyone I spoke with: that the past simply can't be changed."There's nothing we can say to convince anyone," he adds. "There's just a moment when we need to show up."

Excellent article sur Cyberpunk 2077 : avant/pendant/après, ou comment tomber et se relever.

Behind the scenes, all major browser vendors and the CSS specification authors have been working together to deliver tons of highly-requested CSS features. Things like container queries, native CSS nesting, relative color syntax, balanced text, and so much more.

One of these new features is the :has pseudo-class. And, honestly, I wasn’t sure how useful it would be for me. I mostly build webapps using React, which means I tend not to use complex selectors. Would the :has pseudo-class really offer much benefit in this context?

Well, I’ve spent the past few months rebuilding this blog, using all of the modern CSS bells and whistles. And my goodness, I was wrong about :has. It’s an incredibly handy utility, even in a CSS-in-JS context!

In this blog post, I'll introduce you to :has and share some of the most interesting real-world use cases I’ve found so far, along with some truly mindblowing experiments.

Absurde et génial ce qu’il arrive à faire avec des ombres 🤯