I agree with the feeling of mental freeze - My ideal way of working with LLMs when coding is during the prototype/problem-solving phase, where I can dedicate 100% of my mental capacity to the problem at hand and leave the coding to the LLM.
Looking forward to be here!
Today’s sunset was so pretty. Almost like an Instagram filter - but for real.
These new pages are looking so nice!
🚀 Spent ~2 hours upgrading an old client project from Expo 52 → 54 today.
Client was amazed at how smooth it went. This project is not simple—native Expo modules and an external native ePub reader.
Super proud of SDK 54 and the fantastic team at @expo.dev!
expo.dev/blog/expo-sd...
𝝠 Expo SDK 54 is LIVE 🚀
◆ React Native 0.81
◆ Precompiled RN for iOS → faster clean builds
◆ iOS 26 Liquid Glass icons + views
◆ Android 16 target, edge-to-edge default
◆ Router v6 native tabs
◆ Updates: header overrides, progress, reload screen
◆ So much more...
expo.dev/changelog/sd...
👂 It's not quite stable yet but we want to get your eyes (and ears) on this upcoming expo-audio library reference page with examples: docs.expo.dev/versions/lat...
Amazing and inspiring
Interesting read from @aleqsio.com / @expo.dev about Shared object and the Expo Modules API:
expo.dev/blog/the-rea...
I like how BlueSky is entering my life in multiple ways, lastly as a way to give feedback on PRs - @notbrent.dev
No problem at all :)
Makes sense - and looks fun!
Nice! Did you go for Readium, or did you roll your own using webview?
Doing tooling should be fully supported in Readium. Just ping me if you have questions.
I’ve made two RN epub apps using the Readium toolkit (swift/kotlin) - writing a few custom views that takes advantage of this rather mature library has worked out really well.
Love it :)
Appreciate it! <3
Wow… wizard!
👋 bye bye x. Hi Bluesky 😎
Could you use `React.FC<Props>` to define the return type? It should be safe and sound now, shouldn't it?
Same! This is a good place to be!
It is not trivial - but to get an idea of what REA copies you can add logging to the `ShareableObject::toJSValue` method in the native code (Shareables.cpp#233) - just `cout` out the names of the properties it traverses - look for candidates for simplification if this makes sense for you.
I once had a worklet where I was using the React Native `Platform` object to check the OS version - changing this to passing the OS as a stand-alone string made the app so much more snappy since REA was copying the Platform object fully each time the function was called...
Optimizing worklets are often about the cost of copying the captured context of the function - REA automatically detects what you're using inside the worklet function and copies it into the worklet runtime when you call the worklet. Deep objects can add a big performance hit if passed in the ctx.
