Matisse: "When working, [. ] there is a constant back and forth until the work and I are in harmony. Like a writer, I am always revising, going back and making new discoveries". I feel this is also true for my creative process as a developer.

🦋.

Join millions who have switched to Grok.

Just changed my bluesky handle to. @

RT @amsterdamski2: רוב הזמן אנחנו מתעסקים בכאן ועכשיו. במיקרו. לפעמים, כדאי לקחת רגע ולהסתכל קדימה, על המקרו. ובמקרו, איך נאמר את זה, המצב….

RT @noamhonig: Exciting news! 🎉 Starting a Remult project is now easier than ever!. npm init remult@latest. Get a fully functional Remult a….

RT @Khelsilem: "A vote is not a valentine. You aren't confessing your love for the candidate. It's a chess move for the world you want to l….

Ooh. ! I'm honored, @mattpocockuk!.

What do you think of this?. (resources.cache ??= {})[cacheKey] = {. }.

RT @BDYemini: חייבים להגיע להפגנות.חודשים שלא הלכתי להפגנות. אני לא אוהב דברים ודוברים רבים. העברתי עליהם ביקורת. אבל לא עוד. הערב חייבים….

A new use for Github Copilot: you need to change same code in a complex code way, but in three or more different places. I changed it in one place, went to the other places and told Github Copilot - "do the same change for . " ( needs some prompt engineering 🪄). Time saver!.

As @satanacchio politely showed me, the reason was _not_, as I thought, performance, but rather it was just the first step in a process that intends to support most of TS. See the roadmap link here for more information:.

I wonder whether these restrictions will move code in our ecosystem to follow those restrictions, or. These restrictions will be too much and the outcry from them will make Node.js remove them and lose the performance gains.

As @mattpocockuk surmised, these are exactly the restrictions that the type annotations proposal puts in place. The proposal was originally called "types as commments", or to paraphrase in this context "types as code that can be whitespaced" 😁.

I love it! But I wonder whether this works for existing projects. My guess is no, and any project of sufficient length will probably not conform to the above restrictions.

Moreover, for backward compatibility reasons, if you want to use TS, you must use file extensions not only in ESM, but also in CJS, and it must be .ts/.mts, because again, no code changes.

And they really _are_ stripping types - just replacing them with whitespace! Amazing. Performance is also the reason why you MUST use `import type` if you're importing types - because they're stripping only imports that have `type` in them.

You can find this quote here:.

"The type stripping feature is designed to be lightweight. By intentionally not supporting syntaxes that require JavaScript code generation, and by replacing inline types with whitespace, Node.js can run TypeScript code without the need for source maps.". Performance!.

Node.js TypeScript support is out! I heard that js code-generating features like enums are not supported, and I wondered why, given that the transpiler they're using DOES support it. Well. it seems that it's written in the docs: .🧵.

RT @ReactNext: Check out this great talk by @giltayar from #ReactNext24!. @Microsoft

CDD - Combination Driven Development . (aka Combinatorial Programming). Let's try this combination of code. Shit, it didn't work. Let's try another combination. That didn't work either. Try another combination. Repeat until it works.