Hirbod

Thanks 🙏

You won't crash!!!! Just keep shipping Mon frère

Huge PSA for me. Big shift ahead.

Tech with @expo.dev is moving fast. What once felt solid now begs for change. And then, out of nowhere, it felt like the stars aligned. A spark I didn’t see coming lit the way forward.

Standing still stopped making sense.

Time to move.

Oh super nice. That’s even better. Gonna file a PR, ty Kudo

I tried modifying the podspec for two hours, the only thing that worked was the Podfile

React Native fix for libraries failing with ReactCommon/RCTHost.h not found - CNG - Config Plugin - Podfile fix React Native fix for libraries failing with ReactCommon/RCTHost.h not found - CNG - Config Plugin - Podfile fix - README.md

Zeego fails to compile for you with useFrameworks: static? I got you! gist.github.com/hirbod/4b0b0...

@kudochien.dev maybe you know a better solution for this, I think you know best whats up. Not happy with this dangerousMod but at least it unblocks plenty people

Thanks your work on that @kudochien.dev. Truly amazing

But I think I get why this isn’t accessible for screen readers. I’m definitely lacking the skill and knowledge when it comes to this whole topic; the do’s and don’ts.

Our FeedItem is actually a GestureDetector (handles play/pause and double-tap to like), and the RectButtons are placed on top of it—not even nested in the tree. We do have nested pressables, eg in lists where the whole item opens a sheet, but the avatar inside navigates to the profile instead.

I get that, but I believe the „how“ can be optimized

I honestly never even thought about accessibility. We even use the NativeView and NativeText components directly to optimize performance by skipping all of that. We iterate so fast in startups, there’s no room for it until we have PMF.

Generally speaking, I don’t like these automated and expensive lookups. I’d rather have a dev-only warning that forces users to handle accessibility manually. And lookups should bail out fast and have some railguards.

From 300MB to 7GB plus a full hang is even worse. Yeah, it’s not a leak, but an infinite traversal bug. In some very rare and not reliably reproducible cases, nested touchables can trigger this bug and completely freeze the app in our case. Adding a fallback `accessibilityLabel` did the trick.

Yes. Since 2.1.7 it’s amazing and fast

I had a lot of moments reconsidering life choices or just raising alpacas instead of migrating, but it’s finally done. New architecture, @expo.dev SDK 53 (RN 0.79.1), and the fastest React Native app we’ve ever built (and I’ve ever seen!). Thanks to all contributors. Amazing achievement.

This is just insane madness :D.. I really need a break from React Native :D

Imagine, that change made our app the snappiest and fastest react native app I've ever seen. The fucking FPS counter is finally going up, not down when tapping a button. :D

I added a simple "fuck off" as Label and the rare bug is gone. This is just madness and a really bad default by RNGH and React Native. 2/4

I was exploring a hard to debug memory leak in react native for at least 6 hours today. Turns out that when you don't add accessibilityLabel to RectButton or Pressable, it will fucking traverse all children to find a Text node or View with accessibilityLabel. This is insane. 1/4

It looks wrong, I agree. > git reset --hard HEAD~1

🤔

He said „also example ist best of all worlds“ which I translated to „holy grail“. I am not spreading misinformation

Amazing

*not lot

We are on new arch now and I tell you, it’s lot fun 😩. Many many edge cases but we’re close

I try to make a short trip to London while he is there (or vice versa). Maybe coming with family for a weekend

Hey @samuel.bsky.team and @danabra.mov and @tazsingh.com and @mojavad.bsky.social.

@peterp.bsky.social is in London for a few weeks. Super smart and humble guy. He also worked with @hailey.at on new arch for Bluesky. Y’all should definitely meet! Lots of synergy!

Oh Marc provided a fix. I was curious to get some numbers. Our App bundle is too small, the win was very marginal (~2%). 4% for you. Why not.

@samuel.bsky.team worth a try, no? github.com/Expensify/Ap...

github.com/facebook/rea...

But nice illusion