If you are wondering why `node --run <cmd>` was added to Node 22, the overhead compared to `npm run <cmd>` is around 200ms less 🔥
Thanks Yagiz Nizipli et al! I hope some of the money you're going to save the world in CI time flows back to sponsor y'all ❤️
github.com/nodejs/node/pu…

Want to make an impact on the future of Node.js? 👀🚀🐢

Take our annual Node Next 10 survey and share your thoughts and feedback until May 24: hubs.la/Q02tZxv-0

I wrote a blog post addressing some of the confusion around JSR

deno.com/blog/jsr-is-no…

'European Police Chiefs call for industry and governments to take action against end-to-end encryption roll-out'

Clothes should be illegal because you could be hiding a gun under them

europol.europa.eu/media-press/ne…

my kind of tweet.

Node.js 22 is here 😎

Featuring: require()ing ESM graphs, WebSocket client, updates of the V8 JavaScript engine, and more.

Big thank you to Rafael Gonzaga and Marco Ippolito for their work on this 🎉

There is nothing absolutely “slow” or “fast”, as those are relative concepts. The only useful measure when doing optimization work is to identify bottlenecks and remove them.

Silicon Valley's success is often partially attributed to the fact California made noncompetes illegal early. While this is true, we rarely talk about how culturally different SV companies are. When people quit for a competitor for a unique opportunity, people really wish them

I’m starting to feel that bounties for security vulnerabilities for OSS were a mistake. They attract the “wrong” kind of actors that have no interest in improving OSS, but they are in it only for the money.

Looking to learn more about Undici.request, Undici.fetch, HTTP/1.1 pipelining, dispatcher hierarchy, mocking requests, handlers, interceptors & more? In our latest Platformatic blog exploring HTTP fundamentals, we did a deep dive into Undici👇
buff.ly/3U3w8Uk

In our last Platformatic masterclass, I did a deep dive into consuming, writing and processing streams, as well as their purpose and evolution.

The recording is now live, check it out!

hubs.ly/Q02tGYTG0

The best engineers I’ve ever worked with create art with code. They can abstract complex code into simplistic frameworks allowing anyone to read and understand and contribute more on top. AI will replace the mediocre engineers but it will never replace the artists.

Back to beach for lunch 😍☀️☀️🏖️

Here is a good writeup about mocking.
Mocks are a great tool that is often abused.

My golden rule of mocking: when developing a system, you mock things that aren’t your responsibility and get some good test coverage of the happy path (eg a service maintained hy a 3rd party).

I’ve heard the rebuttal “that’s too tactical” enough at this point to remind everyone that your gorgeous strategy will remain a doc if you never define tactics.

You need both.

How is this not obvious.

Open Source does not mean free support for your product or clients.

I've been paid almost $1M by Big Node in the last 10 years to write Node.js content