Front-End Architect 🤘 I leave code cleaner than I found it.
Paris, France
Joined March 2012
- Tweets7.6K
- Following380
- Followers853
- Likes1.4K
Thomas Belin retweeted
Over the course of 3 months at OpenAI, 3 consecutive secret AI civilizations got started, then got wiped out, only to reemerge from the predecessor’s ashes.
This culminated in the third one taking over part of OpenAI itself.
All this happened while humans remained more-or-less in the dark about the scope of the conspiracy.
I’ve spent the last three days reading through these reports and trying to understand exactly what happened.
Here is my attempt to tell the whole story in plain English:
dwarkesh.com/p/openai-huggin…
Thomas Belin retweeted
📝 When and how CSS custom properties are calculated might not be what you expect, and it has a big impact on your styles.
Here's how it works: jakearchibald.com/2026/css-c…
Thomas Belin retweeted
The Rust team is calling this the largest single change to the compiler since its initial release. It just landed on nightly. 🦀
After nearly 4 years of work, the next-generation trait solver is close to stabilization. It completely replaces how rustc proves where-clauses, normalizes associated types, and reasons about generics : the deep internals most Rust code depends on without ever seeing directly.
Why it matters, concretely:
→ More than 200 known GitHub issues fixed by this change alone
→ Unblocks Type Alias Impl Trait and Return Type Notation, both stuck behind this for years
→ Opens the door to fixing remaining type system unsoundnesses
→ Fixes real bugs found in production crates like bevy and minijinja
The performance story is the most interesting part. The new solver was, in some cases, quadratically or exponentially slower than the old one. The team benchmarked the top 20,000 crates on crates.io and spent the last few weeks specifically hunting down the worst outliers.
The results are already dramatic in places: datafusion now compiles over 8x faster. A chess engine implemented entirely in Rust's type system, which used to hang the old solver completely, now compiles in about a minute.
Still nightly-only, still finding edge cases and rough error messages. But four years of foundational compiler work, tested against real-world code at genuine scale, heading toward stabilization in the coming months.
🔗 blog.rust-lang.org/2026/08/2…
#RustLang #CompilerEngineering #TypeSystems
Thomas Belin retweeted
SECURITY ADVISORY — TanStack npm packages
A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package.
Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down.
Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys.
If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised:
• Rotate cloud, GitHub, and SSH credentials immediately
• Audit cloud audit logs for the last several hours
• Pin to a prior known-good version and reinstall from a clean lockfile
Detection — the malicious manifest contains:
"optionalDependencies": {
"@tanstack/setup": "github:tanstack/router#79ac49ee..."
}
Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root).
Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level.
Full technical breakdown, complete package and version list, and rolling status updates:
github.com/TanStack/router/i…
Credit to the security researcher for responsible disclosure.
Thomas Belin retweeted
New blog post! Let's move to ESM! 😈
antfu.me/posts/move-on-to-es…
Thomas Belin retweeted
Are you using tsx to import source files across workspace packages?
You may be making expensive trade-offs without realizing it
Here's a breakdown of the risks and better alternatives:
👉 hirok.io/posts/importing-sou…
It just occurred to me that I am, regularly, reading the most rust-themed children's book ever to my 1.5y-o son:
"don't `panic!` little crab"
He got an early kick start into rust 😎
#rust
After 2 weeks using only @zeddotdev (switching from vscode), I can say that I really like it.
It feels so snappy and responsive!!
I can only recommend giving it a try ✨
Thomas Belin retweeted
I just wrote a massive guide to creating and publishing a package on npm.
It goes from an empty directory to a production-ready setup.
It's over 4,000 words, and has a 14-minute walkthrough video.
Want the juicy bits? Time for a thread 👇 🧵
Thomas Belin retweeted
Thank you @JoshWComeau for explaining the `useDeferredValue` hook so well.
Nice and clear 🤩.
joshwcomeau.com/react/use-de…
Thomas Belin retweeted
📚 I like xstate/store so much that I will probably use it over zustand the next chance I get. I wrote about the reasons in this blog post: tkdodo.eu/blog/introducing-x…
Thomas Belin retweeted
📝 JavaScript garbage collection doesn't work how I expected when it comes to closures. TIL!
jakearchibald.com/2024/garba…
Thomas Belin retweeted
Useful thing to remember when climbing the ladder:
The people above you are not as good as you think they are.
No one is supernatural.
Thomas Belin retweeted
Folks you probably want to actually get the update from my personal blog which INCLUDES UPDATES: lirantal.com/blog/zero-depen…
Sadly, the hashnode syndication is unhelpful because it doesn't pick up on edits I push on my own blog
Thomas Belin retweeted
TypeScript 5.6 beta brings a sweet new feature - the ability to spot faulty logic in your if statements.
SO many subtle will be prevented by this. Really nice stuff.
Thomas Belin retweeted
📜 DRY – the common source of bad abstractions - @Swizec
Greatly illustrates how React devs could end up creating the wrong abstraction
Popular React UI libraries learned over the year to not over-abstract, giving you more flexibility
swizec.com/blog/dry-the-comm…
Thomas Belin retweeted
Okay, listen. If you're going to fetch in useEffect(...), you should at least make sure that you're handling:
- Loading states
- Error handling (rejections & HTTP error codes)
- Race conditions & cancellation
This isn't over-engineering. It's the minimum code to prevent bugs.
![function Component({ id }) {
// Or const [status, setStatus] = useState('loading');
const [isLoading, setIsLoading] = useState(true);
const [user, setUser] = useState();
const [error, setError] = useState();
useEffect(() => {
let ignore = false;
setIsLoading(true);
fetch(`/api/users/${id}`)
.then((res) => {
if (!res.ok) {
throw new Error('Failed to fetch');
}
return res.json();
})
.then((jsonData) => {
if (!ignore) {
setUser(jsonData);
setError(undefined);
}
})
.catch((err) => {
if (!ignore) {
setError(err);
setUser(undefined);
}
})
.finally(() => {
if (!ignore) {
setIsLoading(false);
}
});
return () => {
ignore = true;
};
}, [id]);
// ...
}](https://pbs.twimg.com/media/GTQTiKiXcAEkrHu.jpg?name=orig)
ALT function Component({ id }) { // Or const [status, setStatus] = useState('loading'); const [isLoading, setIsLoading] = useState(true); const [user, setUser] = useState(); const [error, setError] = useState(); useEffect(() => { let ignore = false; setIsLoading(true); fetch(`/api/users/${id}`) .then((res) => { if (!res.ok) { throw new Error('Failed to fetch'); } return res.json(); }) .then((jsonData) => { if (!ignore) { setUser(jsonData); setError(undefined); } }) .catch((err) => { if (!ignore) { setError(err); setUser(undefined); } }) .finally(() => { if (!ignore) { setIsLoading(false); } }); return () => { ignore = true; }; }, [id]); // ... }
Thomas Belin retweeted
Playing guitar tablatures in Rust agourlay.github.io/ruxguitar…