birch_js's profile picture. All-terrain dev working across web, native, TV, and backend for over a decade, with a particular masochism for React Native and NativeScript.

Jamie Birch

@birch_js

All-terrain dev working across web, native, TV, and backend for over a decade, with a particular masochism for React Native and NativeScript.

مثبتة

Pretty surreal to see @theo covering my article! I caught it live, so can assure it was a fun watch from my point of view. 🍿 Theo also caught the fact that React Native deploys to e-ink Kindles and PlayStations, which I overlooked! Tempted to add those to the addendum now 😄

birch_js's tweet image. Pretty surreal to see @theo covering my article!

I caught it live, so can assure it was a fun watch from my point of view. 🍿

Theo also caught the fact that React Native deploys to e-ink Kindles and PlayStations, which I overlooked! Tempted to add those to the addendum now 😄

If you're going to make a barrel module, at least do it with style

birch_js's tweet image. If you're going to make a barrel module, at least do it with style

Best part of tech meetups is shutting up about the tech and going to a karaoke bar

birch_js's tweet image. Best part of tech meetups is shutting up about the tech and going to a karaoke bar

At #ReactNativeJP, Shunsuke-san revealed that the following Amazon devices, plus the new Fire TV 4K Select, all run React Native.

birch_js's tweet image. At #ReactNativeJP, Shunsuke-san revealed that the following Amazon devices, plus the new Fire TV 4K Select, all run React Native.

Jamie Birch أعاد

React Native’s networking stack is built on native APIs: - iOS and macOS: NSURLRequest - Android: OkHttpClient - Windows: winrt::Windows::Web::Http There’s a “last mile” of non-native code to expose it as familiar JavaScript APIs, sure, but the hot path is all native.

birch_js's tweet image. React Native’s networking stack is built on native APIs:

- iOS and macOS: NSURLRequest
- Android: OkHttpClient
- Windows: winrt::Windows::Web::Http

There’s a “last mile” of non-native code to expose it as familiar JavaScript APIs, sure, but the hot path is all native.
birch_js's tweet image. React Native’s networking stack is built on native APIs:

- iOS and macOS: NSURLRequest
- Android: OkHttpClient
- Windows: winrt::Windows::Web::Http

There’s a “last mile” of non-native code to expose it as familiar JavaScript APIs, sure, but the hot path is all native.

Learning the latest state of React Native DevTools from @huntie at React Native Japan!

birch_js's tweet image. Learning the latest state of React Native DevTools from @huntie at React Native Japan!

Learning the right way to consistently vertically align text across both iOS and Android thanks to @mrtry_'s talk at React Native Japan! The key to victory is the `includeFontPadding` style! Also iOS doesn't have `textAlignVertical`? 😮


don't worry, sheeple devs always just parrot popular claims without substantiating them

birch_js's tweet image. don't worry, sheeple devs always just parrot popular claims without substantiating them

I hear this a lot, but in my experience React Native is very fast and can be even faster than native apps. Is there any evidence it’s slow, or is this just a common misconception?



OSS contributions are measured in bread machines

Node & TypeScript excitement 😉 Marco tells the story of implementing Type Stripping support in Node. It involves a lot of collaboration across the JS ecosystem. 🔷 First cut took 20 days (fast for Node) 🔷 TS delivered flags to ease adoption 🔷 Marco's reward: a bread machine



If you ever feel like being truly hazed, try asking an LLM to implement streaming file uploads for the Electron main process. It's a pinball machine that ricochets between being wrong for every possible implementation of networking that Electron has access to.


Nice! I’d say when comparing Expo / React Native to single-platform dev, some easy things become hard, yet some hard things become easy. Personally, I greatly prefer the tradeoff that Expo / RN strikes. I like writing TS, developing in VSC and expressing UIs in React + Tailwind.

👀 First time built something using Expo. Was quite a hassle compared to SwiftUI lol

buildwithdjdev's tweet image. 👀 First time built something using Expo. Was quite a hassle compared to SwiftUI lol


Businesses need to get into the habit of valuing engineering hours properly. Sure, CI/CD and SaaS offerings do cost a certain amount, but spending weeks of engineering time naïvely trying to implement a fraction of what something like EAS gives you is just short-sighted.

Team debated: GitHub Actions vs Jenkins for CI/CD. Jenkins advocates: - We already have it - More powerful - Self-hosted - Free (ignoring ops time) GitHub Actions advocates: - YAML in repo - No server to maintain - Modern UI - Faster Decision process: - Ran both for 1 month -…



This one was tough. Lots of challenges when your node_modules itself is a symlink, and even more so for out-of-tree platforms. Got to demonstrate various Metro debugging techniques. Was able to get something working thanks to Microsoft's rnx-kit, though!

Now streaming! 🎙️ I'll be hacking on my unreleased dev tool, React Native Fiddle tonight. Come learn advanced Metro debugging! Link below.

birch_js's tweet image. Now streaming! 🎙️

I'll be hacking on my unreleased dev tool, React Native Fiddle tonight. Come learn advanced Metro debugging!

Link below.
birch_js's tweet image. Now streaming! 🎙️

I'll be hacking on my unreleased dev tool, React Native Fiddle tonight. Come learn advanced Metro debugging!

Link below.


Loading...

Something went wrong.


Something went wrong.