Matteo Collina

@platformatic Co-Founder & CTO, @nodejs TSC Chair, Lead maintainer @fastifyjs, Board @OpenJSF, Conference Speaker, Ph.D. Past: @nearform. Views are my own.

[Matteo Collina @matteocollina]

🧵 I wrote almost 19,000 lines of code for a Virtual File System in @nodejs core using Claude Code. It started over Christmas and has been refined over almost three months of review.

A collaborator challenged whether AI-assisted contributions can meet the DCO requirements.

Here's what happened, and why it matters for all of open source.

[Gergely Orosz @GergelyOrosz]

While impressive, for 99% of companies, justifying a one-off $150K+ spend on a single migration is just not realistic.

Even tho they will justify 3 devs spending a year working on it… while also doing other work (incl product work, planning, support etc), as they always do.

[Rob Palmer @robpalmer2]

TypeScript 7.0 is out 🎉

It's the 10x faster Go-based port 🔥

🔷 `tsc6` is for side-by-side API access
🔷 --checkers sets checker thread count
🔷 --singleThreaded keeps parsing/emit/checking together
🔷 TS 6.0 deprecations are hard errors
🔷 API access is planned for TS 7.1

[TypeScript @typescript]

📣 The moment is here. 📣

TypeScript 7 is officially released! 7️⃣

https://t.co/D7Mbq7vWpy

[Jay @jayair]

We've usually stayed away from model comparisons but 5.6 vs Fable is a unique situation

We've never had a case where the team is so completely convinced on which one is better

Here's the timeline of our experience with it

- We test early versions of 5.6 for a couple of weeks and have a great time, it feels like a step change improvement, enabling new workflows
- We get to try Fable and don't think it's not as good, I personally would take this experience with a grain of salt, there tends to be a bias when trying a new model when you already like another
- Fable and 5.6 are taken away because of the regulatory issues
- Our team is literally depressed that 5.6 is gone, we are looking for anything that could even partly replace it
- Fable comes back, and here's where it gets interesting, you would think Fable would be enough, but no, the team is still depressed that 5.6 isn't available
- Then 5.6 comes back and it's immediately clear that it's just way better than Fable

This situation was unique in that it was the closest we've ever gotten to having an unbiased comparison of two models

[Kenton Varda @KentonVarda]

I just declared a moratorium against AI-written change descriptions (e.g. PR and commit messages, also issues/tickets) from my team.

AI was writing change descriptions that were worse than useless to me as I tried to review PRs: outlining details of the code that could easily be seen by looking at the code, but omitting the higher-level framing needed to understand broadly what the code is doing.

I think people like having AI write these things because the output looks structured and thorough, which makes it feel professional in a way. But this isn't actually valuable. Concise, high-level descriptions are better for everyone. If I need to use my own AI to interpret what your AI wrote then something is wrong. Let AI write code, sure, but for the description, I'd rather see your prompt than your output.

We could maybe have extended agents.md with guidelines on writing descriptions, but this seemed a bit pointless since a good, concise change description only takes a few minutes to write -- not a significant time savings to delegate to AI. At least, it doesn't take long if you understand the code -- and if you don't understand the code, then I'm definitely not merging it.

[antirez @antirez]

So @theo published a YouTube video about local inference and its hard limits (you often can *not* run the fancy open weight models locally) and I agree with every word, but then with two M5 Max 128GB systems and RDMA I'm at 50 token/sec with DeepSeek v4 Flash Q5 even without speculative decoding (that wins another 15/20% max, it's a very sparse model, single session, no magic tricks). And I'm starting to thing we are actually exactly at the turning point of all that.

[Matteo Collina @matteocollina]

Your Node.js Gateway It's Doing Twice the Work https://t.co/YxTK9cQTv9

[@levelsio @levelsio]

🇪🇺 The EU is now for the 6th time trying to force Chat Control through which lets them scan ALL your private messages, photos and emails without a warrant

Implictly showing the EU is not democratic and not about what the people of Europe want, because once a law is rejected, you just re-submit it until nobody is watching and it's passed

November 2023: ❌ Chat Control is rejected
June 2024: ❌ Chat Control is rejected
October 2025: ❌ Chat Control is rejected
November 2025: ❌ Chat Control is rejected
March 2026: ❌ Chat Control is rejected
July 2026: 📝 Chat Control is back

Even the EU's own lawyers stated Chat Control is unconstitutional: "generalised message scanning is incompatible with Article 7 of the EU Charter"

You have to wonder why the EU is so adament about reading your private chats, right?

[David Cramer @zeeg]

When people say models are good at coding they mean they’re good like an L3 at IBM, not like an L8 at FAANG

[John-David Dalton @jdalton]

Node 20 is EOL. I hear ya, I've had folks requesting Node 18 support still. However, benefitting from stricter pnpm while on EOL Node is like putting a lock on a door with the windows open and roof missing. The time to begin to migrate off was in its 1.5 year maintenance window (October 2024 – April 2026)

• https://t.co/WvwjCa58l5
• https://t.co/HovaSM8DO3
• https://t.co/B8kyn3UAom

[Matteo Collina @matteocollina]

@lucalanziani 0 days. They are agent frameworks now 😝

[Matteo Collina @matteocollina]

@lucamaraschi @p_insogna Caching plus deduplication is the difference between a viral moment and a very bad day.

Paolo built this into Platformatic Gateway so you get the protection without touching your backend.

Full episode, July 8th 👇
🔗 https://t.co/xPhzTbK7Zc

[Matteo Collina @matteocollina]

🔥 NEW BANTER: "Your Node.js Gateway Is Doing Twice the Work"

You launch. Thousands hit the same link at once. The cache is cold. And your app builds the exact same response hundreds of times in parallel.

@lucamaraschi and I sit down with @p_insogna to make it stop.

📅 July 8th

[Matteo Collina @matteocollina]

@lucamaraschi @p_insogna And you can prove it's working.

The right metrics show duplicate requests collapsing into single upstream calls, and tell you what to watch as you roll it out in production.

Caching protects you from the next request. Deduplication protects you during this one. You want both.