Jamie Birch
@shirakaba.bsky.social
💼 Software Engineer 👨🔧 Cross-platform hobbyist 📱NativeScript TSC 📺 ex-Smart TV dev 👨🔬 ex-virologist 🇯🇵 日本語 🆗
Reposted by Jamie Birch
🌠 JS Rising Stars 2025 are live!
Huge thanks to our amazing guest writers:
@rwieruch.bsky.social (React)
@danielroe.dev (Vue, coming soon 😉)
@sebastienlorber.com (Tooling)
@jherr.dev (AI)
@shirakaba.bsky.social (Mobile)
Your insights bring depth to the report!
risingstars.js.org/2025/en
Huge thanks to our amazing guest writers:
@rwieruch.bsky.social (React)
@danielroe.dev (Vue, coming soon 😉)
@sebastienlorber.com (Tooling)
@jherr.dev (AI)
@shirakaba.bsky.social (Mobile)
Your insights bring depth to the report!
risingstars.js.org/2025/en
2025 JavaScript Rising Stars
A complete overview of the JavaScript landscape in 2025: trends about frontend, fullstack and Node.js frameworks, React and Vue.js ecosystems, build tools, state management...
risingstars.js.org
January 4, 2026 at 10:48 PM
🌠 JS Rising Stars 2025 are live!
Huge thanks to our amazing guest writers:
@rwieruch.bsky.social (React)
@danielroe.dev (Vue, coming soon 😉)
@sebastienlorber.com (Tooling)
@jherr.dev (AI)
@shirakaba.bsky.social (Mobile)
Your insights bring depth to the report!
risingstars.js.org/2025/en
Huge thanks to our amazing guest writers:
@rwieruch.bsky.social (React)
@danielroe.dev (Vue, coming soon 😉)
@sebastienlorber.com (Tooling)
@jherr.dev (AI)
@shirakaba.bsky.social (Mobile)
Your insights bring depth to the report!
risingstars.js.org/2025/en
I've sent you an email with a job posting 😊
November 11, 2025 at 9:50 AM
I've sent you an email with a job posting 😊
It's even worse on the latest releases of Safari. The scroll container doesn't even render! Wasn't expecting that.
macOS Tahoe 26.0 (25A353):
- Left: Safari 26.0 (21622.1.22.11.14).
- Middle: Safari on iOS 26.0.
- Right: Safari TP 227 (WebKit 21623.1.5).
Linking this as well.
macOS Tahoe 26.0 (25A353):
- Left: Safari 26.0 (21622.1.22.11.14).
- Middle: Safari on iOS 26.0.
- Right: Safari TP 227 (WebKit 21623.1.5).
Linking this as well.
September 17, 2025 at 1:09 AM
It's even worse on the latest releases of Safari. The scroll container doesn't even render! Wasn't expecting that.
macOS Tahoe 26.0 (25A353):
- Left: Safari 26.0 (21622.1.22.11.14).
- Middle: Safari on iOS 26.0.
- Right: Safari TP 227 (WebKit 21623.1.5).
Linking this as well.
macOS Tahoe 26.0 (25A353):
- Left: Safari 26.0 (21622.1.22.11.14).
- Middle: Safari on iOS 26.0.
- Right: Safari TP 227 (WebKit 21623.1.5).
Linking this as well.
It seems it doesn't require a mix of horizontal-tb and vertical-rl. Purely vertical-rl is enough. Will link this video in the Bugzilla report.
September 17, 2025 at 1:01 AM
It seems it doesn't require a mix of horizontal-tb and vertical-rl. Purely vertical-rl is enough. Will link this video in the Bugzilla report.
I think I've got a repro! Both a scrolling issue (as the pan gesture passes straight through the overlay) and a rendering issue (as the bottom portion of the overlay unexpectedly goes black).
Just cleaning it up, then will file it.
Just cleaning it up, then will file it.
September 16, 2025 at 11:50 PM
I think I've got a repro! Both a scrolling issue (as the pan gesture passes straight through the overlay) and a rendering issue (as the bottom portion of the overlay unexpectedly goes black).
Just cleaning it up, then will file it.
Just cleaning it up, then will file it.
Thank you! 🙇♂️
@smfr.bsky.social did offer to raise visibility – I just hadn't had any time to try to make a repro, sorry! I'm trying to make a repro now, just failing to work out the exact combination of factors behind the ebook that was causing the issue.
bsky.app/profile/smfr...
@smfr.bsky.social did offer to raise visibility – I just hadn't had any time to try to make a repro, sorry! I'm trying to make a repro now, just failing to work out the exact combination of factors behind the ebook that was causing the issue.
bsky.app/profile/smfr...
I'd be happy to get WebKit folks to look at this if you're willing to share you app and the content. You can do so by using Feedback Assistant to file an issue, or bugs.webkit.org for things that are OK to be public.
WebKit Bugzilla
bugs.webkit.org
September 16, 2025 at 11:27 PM
Thank you! 🙇♂️
@smfr.bsky.social did offer to raise visibility – I just hadn't had any time to try to make a repro, sorry! I'm trying to make a repro now, just failing to work out the exact combination of factors behind the ebook that was causing the issue.
bsky.app/profile/smfr...
@smfr.bsky.social did offer to raise visibility – I just hadn't had any time to try to make a repro, sorry! I'm trying to make a repro now, just failing to work out the exact combination of factors behind the ebook that was causing the issue.
bsky.app/profile/smfr...
This is another big deal. We can write React Native modules in Rust now, with a standard approach rather than deep, specialist expertise.
Heck, we can code in C, C++, C#, Swift, Zig, Go, too – pick whichever you feel most comfortable in!
bsky.app/profile/krae...
Heck, we can code in C, C++, C#, Swift, Zig, Go, too – pick whichever you feel most comfortable in!
bsky.app/profile/krae...
Personally, I'm most excited about the prospect of using code-generation of bindings between native Rust libraries and the JavaScript engine! Powered by the napi.rs project!
July 10, 2025 at 1:35 PM
This is another big deal. We can write React Native modules in Rust now, with a standard approach rather than deep, specialist expertise.
Heck, we can code in C, C++, C#, Swift, Zig, Go, too – pick whichever you feel most comfortable in!
bsky.app/profile/krae...
Heck, we can code in C, C++, C#, Swift, Zig, Go, too – pick whichever you feel most comfortable in!
bsky.app/profile/krae...
This is it, the most consequential evolution of React Native since JSI and New Arch. Through Node-API, we can:
- unit-test native modules in Node.js
- code-share with Electron
- use NativeScript inside React Native
- prebuild community modules
- achieve 7-second app builds
- unit-test native modules in Node.js
- code-share with Electron
- use NativeScript inside React Native
- prebuild community modules
- achieve 7-second app builds
July 10, 2025 at 1:34 PM
This is it, the most consequential evolution of React Native since JSI and New Arch. Through Node-API, we can:
- unit-test native modules in Node.js
- code-share with Electron
- use NativeScript inside React Native
- prebuild community modules
- achieve 7-second app builds
- unit-test native modules in Node.js
- code-share with Electron
- use NativeScript inside React Native
- prebuild community modules
- achieve 7-second app builds
See this PR in which I set up Metro to special-case certain file extensions.
I transpile .wvts files from TS to JS, then wrap in a string (to inject into a WebView).
In your case, you’d transpile .purs files to JS ESM modules, without wrapping in a string afterwards.
github.com/shirakaba/pa...
I transpile .wvts files from TS to JS, then wrap in a string (to inject into a WebView).
In your case, you’d transpile .purs files to JS ESM modules, without wrapping in a string afterwards.
github.com/shirakaba/pa...
Merge pull request #1 from shirakaba/source-assets · shirakaba/paranovel-two@16fc303
support "source assets" to improve DX of injecting scripts into the WebView
github.com
June 11, 2025 at 5:46 AM
See this PR in which I set up Metro to special-case certain file extensions.
I transpile .wvts files from TS to JS, then wrap in a string (to inject into a WebView).
In your case, you’d transpile .purs files to JS ESM modules, without wrapping in a string afterwards.
github.com/shirakaba/pa...
I transpile .wvts files from TS to JS, then wrap in a string (to inject into a WebView).
In your case, you’d transpile .purs files to JS ESM modules, without wrapping in a string afterwards.
github.com/shirakaba/pa...
The number of people who didn’t even bother reading Anders and Ryan’s summaries of how the language evaluation went, and just parrot bastardised takes by lazy influencers, is just aggravating
March 13, 2025 at 12:47 PM
The number of people who didn’t even bother reading Anders and Ryan’s summaries of how the language evaluation went, and just parrot bastardised takes by lazy influencers, is just aggravating
I've just uploaded the lightning talk I gave on build profiling at React Native Meetup #20 (featuring Meta and Callstack) on Feb 18th.
- English: speakerdeck.com/shirakaba/bu...
- Japanese (original): speakerdeck.com/shirakaba/bi...
Someone should really look into the cmake settings for Android!
- English: speakerdeck.com/shirakaba/bu...
- Japanese (original): speakerdeck.com/shirakaba/bi...
Someone should really look into the cmake settings for Android!
March 5, 2025 at 12:02 PM
I've just uploaded the lightning talk I gave on build profiling at React Native Meetup #20 (featuring Meta and Callstack) on Feb 18th.
- English: speakerdeck.com/shirakaba/bu...
- Japanese (original): speakerdeck.com/shirakaba/bi...
Someone should really look into the cmake settings for Android!
- English: speakerdeck.com/shirakaba/bu...
- Japanese (original): speakerdeck.com/shirakaba/bi...
Someone should really look into the cmake settings for Android!
Now streaming! We're going to be recreating the Xcode UI as a React DOM + Tailwind component for teaching purposes.
In this screenshot, the top bit is what I've completed so far, while the bottom bit is the reference image that we need to reproduce!
Stream here:
youtube.com/live/6jmLZ72...
In this screenshot, the top bit is what I've completed so far, while the bottom bit is the reference image that we need to reproduce!
Stream here:
youtube.com/live/6jmLZ72...
March 5, 2025 at 5:45 AM
Now streaming! We're going to be recreating the Xcode UI as a React DOM + Tailwind component for teaching purposes.
In this screenshot, the top bit is what I've completed so far, while the bottom bit is the reference image that we need to reproduce!
Stream here:
youtube.com/live/6jmLZ72...
In this screenshot, the top bit is what I've completed so far, while the bottom bit is the reference image that we need to reproduce!
Stream here:
youtube.com/live/6jmLZ72...
More progress on my Xcode classroom – a React DOM + Tailwind v4 component for making tutorials that involve Xcode!
Lately I've been improving window resizing. I wanted to match how Xcode collapses labels (yet not icons) when space is limited. Keep your eyes on the run destination!
Lately I've been improving window resizing. I wanted to match how Xcode collapses labels (yet not icons) when space is limited. Keep your eyes on the run destination!
March 5, 2025 at 4:43 AM
More progress on my Xcode classroom – a React DOM + Tailwind v4 component for making tutorials that involve Xcode!
Lately I've been improving window resizing. I wanted to match how Xcode collapses labels (yet not icons) when space is limited. Keep your eyes on the run destination!
Lately I've been improving window resizing. I wanted to match how Xcode collapses labels (yet not icons) when space is limited. Keep your eyes on the run destination!
Reposted by Jamie Birch
my understanding is that you are also not allowed to just write css anymore and you have to use some sort of meteorological phenomenon to manage it for you
February 28, 2025 at 9:53 PM
my understanding is that you are also not allowed to just write css anymore and you have to use some sort of meteorological phenomenon to manage it for you
Whoops, obviously forgot to rename "compendium" -> "paranovel" for the screenshot.
Well, there's plenty of other glaring errors in there anyway 😅
Well, there's plenty of other glaring errors in there anyway 😅
February 26, 2025 at 2:07 PM
Whoops, obviously forgot to rename "compendium" -> "paranovel" for the screenshot.
Well, there's plenty of other glaring errors in there anyway 😅
Well, there's plenty of other glaring errors in there anyway 😅
Continuing work on my fake in-browser Xcode mockup for making React Native tutorials. Spot the difference!
Built using React DOM and Tailwind v4. I can't use SFSymbols due to licensing, so I'm doing the best I can with Material Icons/Symbols 😅 it somewhat works!
Built using React DOM and Tailwind v4. I can't use SFSymbols due to licensing, so I'm doing the best I can with Material Icons/Symbols 😅 it somewhat works!
February 26, 2025 at 2:05 PM
Continuing work on my fake in-browser Xcode mockup for making React Native tutorials. Spot the difference!
Built using React DOM and Tailwind v4. I can't use SFSymbols due to licensing, so I'm doing the best I can with Material Icons/Symbols 😅 it somewhat works!
Built using React DOM and Tailwind v4. I can't use SFSymbols due to licensing, so I'm doing the best I can with Material Icons/Symbols 😅 it somewhat works!
I've been making a docs site to share everything I've learned as a fullstack dev. 📜
When it came to documenting React Native, I decided that instead of using static screenshots of Xcode, it would be nice to have an interactive mockup of Xcode in-browser. So I began making one!
When it came to documenting React Native, I decided that instead of using static screenshots of Xcode, it would be nice to have an interactive mockup of Xcode in-browser. So I began making one!
February 25, 2025 at 10:56 AM
I've been making a docs site to share everything I've learned as a fullstack dev. 📜
When it came to documenting React Native, I decided that instead of using static screenshots of Xcode, it would be nice to have an interactive mockup of Xcode in-browser. So I began making one!
When it came to documenting React Native, I decided that instead of using static screenshots of Xcode, it would be nice to have an interactive mockup of Xcode in-browser. So I began making one!
Reposted by Jamie Birch
Speeding up the JavaScript ecosystem part 11 is here! This time we're looking at:
Extending Rust tools with JavaScript plugins
marvinh.dev/blog/speedin...
Extending Rust tools with JavaScript plugins
marvinh.dev/blog/speedin...
Speeding up the JavaScript ecosystem - Rust and JavaScript Plugins
Up until recently, supporting JavaScript in Rust based tools has been deemed not worth it. The main concern is the overhead of the de-/serialization cost when sending data back and forth. But there is...
marvinh.dev
February 23, 2025 at 3:37 PM
Speeding up the JavaScript ecosystem part 11 is here! This time we're looking at:
Extending Rust tools with JavaScript plugins
marvinh.dev/blog/speedin...
Extending Rust tools with JavaScript plugins
marvinh.dev/blog/speedin...
Very cool, and great writing as always. I’ve heard this “arrays, not trees” sentiment for AST-traversal come up a few times in the last couple years.
I heard on the Devtools podcast that Tailwind and/or VoidZero (can’t recall) are investigating the same. The idea came up on Hacker News too.
I heard on the Devtools podcast that Tailwind and/or VoidZero (can’t recall) are investigating the same. The idea came up on Hacker News too.
February 24, 2025 at 3:08 AM
Very cool, and great writing as always. I’ve heard this “arrays, not trees” sentiment for AST-traversal come up a few times in the last couple years.
I heard on the Devtools podcast that Tailwind and/or VoidZero (can’t recall) are investigating the same. The idea came up on Hacker News too.
I heard on the Devtools podcast that Tailwind and/or VoidZero (can’t recall) are investigating the same. The idea came up on Hacker News too.
Helping bring Node-API to React Native 🫡
February 22, 2025 at 3:41 PM
Helping bring Node-API to React Native 🫡
Join us, you'll never have time to spare for language-learning ever again haha
February 22, 2025 at 3:22 PM
Join us, you'll never have time to spare for language-learning ever again haha
Just successfully built a Node-API module for iOS, tvOS, visionOS, and macOS (with and without Catalyst), all packaged into a single XCFramework 🥹
Had to dig through the cmake internals to figure out how to build for Catalyst properly, but got there in the end! 😮💨
Had to dig through the cmake internals to figure out how to build for Catalyst properly, but got there in the end! 😮💨
February 22, 2025 at 3:21 PM
Just successfully built a Node-API module for iOS, tvOS, visionOS, and macOS (with and without Catalyst), all packaged into a single XCFramework 🥹
Had to dig through the cmake internals to figure out how to build for Catalyst properly, but got there in the end! 😮💨
Had to dig through the cmake internals to figure out how to build for Catalyst properly, but got there in the end! 😮💨