I’ll forgive anything, just please implement ternary operators in GitHub Actions workflows

That sweet, sweet email just before Christmas informing that the Apple Developer Program License Agreement has been updated, as Apple are being forced to comply with new anti-competition regulation in Japan 🎄

Sadly, Fortnite will not return to iOS in Japan in 2025 as promised. Apple was required to open up iOS to competing stores today, and instead of doing so honestly, they have launched another travesty of obstruction and lawbreaking in gross disrespect to the government and people of Japan. Apple chose poorly. Again.

Look how much power you get with a simple CSS query casually implemented in Chromium as just another update. I don’t think React Native will ever catch up with web browsers.

~65.4% of transform time in @Expo is spent removing common language features that aren't supported in the Hermes engine. Upgrading to Hermes v1—in SDK 55—means all of the following transforms could be removed (assuming block scoping and async generators are enabled). This is partially why any bundler you use to target Hermes ends up being slow. Supporting this much Babel also makes it hard to conditionally use Babel alternatives for node modules. Major speed-ups are coming to Expo bundle times next year!

The long-awaited Standard JSON Schema spec has been published! 🔥 "Standard Schema for JSON Schema conversion" 🔥 day-one support from Zod, ArkType, and Valibot 🔥 support coming soon to AI SDK, Tanstack AI, and the MCP SDK

This year’s official Microsoft Ugly Sweater has “sold out in record time”, so they’re producing a second run for January

Just found this spare flash storage in my old camera bag. Imagine how much it’s worth now

One thing I like about compiled languages is that it can tell you definitively "this thing throws, so handle it or else". With JavaScript, I like the "neverthrow" philosophy. Catch errors at the source and return a Result.Err() instead. Don't make it the caller's problem!

Dramatic shot of me asking what the metal fish is for

Very fun day hanging out with @birch_js at a Japanese folk house museum. It's so awesome when online heroes are super cool in real life ❤️

Stream here: youtube.com/live/-XcquTmWzKY…

Now streaming my writing process! 🎙️ I'll be writing my frontend predictions for 2026. Come keep me company and give me your thoughts for 2026 as well! Link below.

sounds fake but I'm starting a company with my nemesis David E. ArkType and our first hire is @AndaristRake and our first product is now in beta

Meeting with the legend himself, @jmeistrich! Can’t wait to catch up again 😊

Let me take a moment to celebrate this monumental moment for React Native: This is the first release EVER without ANY breaking change! Updating 0.82 -> 0.83 will be as easy as changing the version in your package.json Our path to stability is bright ahead!

As a follow up to yesterdays post about RN Text memory consumption, I wanted to share some further details: On iOS, the Text component doesn't use native primitives like UILabel/UITextView but is rather a custom UIView subclass that renders text in a way similar to UITextView.

Some fun UTF-8 history, as told by Rob Pike from Google in a 2003 email. "UTF-8 was designed, in front of my eyes, on a placemat in a New Jersey diner one night in September or so 1992. What happened was this. We had used the original UTF from ISO 10646 to make Plan 9 support 16-bit characters, but we hated it. We were close to shipping the system when, late one afternoon, I received a call from some folks, I think at IBM - I remember them being in Austin - who were in an X/Open committee meeting. They wanted Ken [Thompson] and me to vet their FSS/UTF design. We understood why they were introducing a new design, and Ken and I suddenly realized there was an opportunity to use our experience to design a really good standard and get the X/Open guys to push it out. We suggested this and the deal was, if we could do it fast, OK. So we went to dinner, Ken figured out the bit-packing, and when we came back to the lab after dinner we called the X/Open guys and explained our scheme. We mailed them an outline of our spec, and they replied saying that it was better than theirs (I don't believe I ever actually saw their proposal; I know I don't remember it) and how fast could we implement it? I think this was a Wednesday night and we promised a complete running system by Monday, which I think was when their big vote was. So that night Ken wrote packing and unpacking code and I started tearing into the C and graphics libraries. The next day all the code was done and we started converting the text files on the system itself. By Friday some time Plan 9 was running, and only running, what would be called UTF-8. We called X/Open and the rest, as they say, is slightly rewritten history. Why didn't we just use their FSS/UTF? As I remember, it was because in that first phone call I sang out a list of desiderata for any such encoding, and FSS/UTF was lacking at least one - the ability to synchronize a byte stream picked up mid-run, with less that one character being consumed before synchronization. Because that was lacking, we felt free - and were given freedom - to roll our own."

My talk with @SaadNajmi at @RNLConf is up! You might have seen me talking about React Native macOS a lot. This is my argument for why we should take React Native on desktop seriously and make apps good again✌️. And Saad shows off the cool new stuff! youtube.com/watch?v=XE7yKGDs…