Pearce Keesling

@rtfeldman I'm curious, do you think Zed has had an uptick? From what I understand the disconnect mostly stems from Jevon's paradox and most of the productivity gains are going towards increasingly lower priority items so the high level mission velocity is not affected

In the past 3 years, I haven't noticed any uptick in release speed for software I use. If productivity is increasing, I can't tell as an end user. I have noticed decreases in uptime, increases in bugs, and a HUGE increase in people bragging about how many PRs per day they land.

@joreilly Looks like kotlinJS is also supported! >JS and WasmJS Support

New Room 3.0 alpha release now supports Kotlin/Wasm #KMP #3.0.0-alpha01" target="_blank" rel="nofollow noopener">developer.android.com/jetpack/androi…

@jetbrains Vim mode 👀? Pretty sure fleet had first class vim mode so I bet it's hiding somewhere in that codebase

With Air, you can use Codex, Claude Agent, Gemini CLI, and Junie – all with a single JetBrains AI Pro or Ultimate subscription. Prefer your own provider? Bring your OpenAI, Anthropic, or Google API keys or subscriptions and stay flexible. Try Air: jb.gg/4dhmrw

@GregorySchier Are MCPs working for you? I booted it up and all my mcps are labelled as "unavailable" but they are definitely working in codex.

Looks like JetBrains found a use for their abandoned Fleet IDE rewrite

@NativeScript @tan_stack @solid_js @vite_js Is predictive back planned?

@tan_stack @solid_js @vite_js Beautiful on Android

Type-safe routing, natively. @tan_stack router + @solid_js w/@vite_js 👉 iOS 📱 Android 🤖 visionOS 🥽

@ipla03 @callstackio @grabbou > While hidden, children still re-render in response to new props, albeit at a lower priority than the rest of the content. #activity" target="_blank" rel="nofollow noopener">react.dev/reference/reac…

@ipla03 @callstackio @grabbou From what I understand Activity will still render just at a much lower priority so it doesn't block renders for "active" components. Freeze doesn't render at all so if you return to that component and unfreeze you'll now have to render to "catch up"

We explored using `<Activity mode="hidden">` in React Navigation 8. The problem: it hides the UI entirely, which breaks swipe-back gestures. Here’s a workaround that keeps screens visible while still unmounting effects. Read the article ⬇️ Link in the comments!

@betomoedano Most of the ones we had problems with we don't use anymore and replaced with in-house solutions because we got tired of the color issues, but gradients, victory charts, component libraries like react-native-paper all had problems

@keeslinp Which libraries?

"use platform colors"

@kafara_kacper @satya164 Status update: Still broken 🫠

@kafara_kacper @satya164 Here are three touchable issues on android github.com/facebook/react… github.com/facebook/react… Open PRs: github.com/facebook/react… github.com/facebook/react… Iirc screens was loosely involved because screens moves around elements.

How many are still using the old architecture? x.com/swmansion/stat…

@kafara_kacper @satya164 This was another fun one that does appear to have been fixed 🎉 github.com/facebook/react…

@birch_js I'll bet when they considered what could be cut in order to make their 2026 alpha release this seemed like an obvious option. Maybe longterm a different language makes sense but in the next year or two it'd almost certainly be a net negative for productivity

I just heard that Ladybird is no longer pursuing adopting Swift into their C++ codebase. It sounds like there were a lot of blockers, to be fair. Many, but not all, had been cleared by Swift 6.2, though, so I wonder what drove this decision. I suppose we’ll hear in due course!

@jmeistrich I have an open PR right now removing the last of our FlashList usage (nothing against FlashList fwiw, it just makes our new-arch migration harder). Definitely going to check this out once it's out.

Legend List v3 is now in production on web + mobile! It’s faster and better, and on web it powers chat with bidirectional infinite scrolling and no scroll jank 🎉. The last big step is strict typing on both web and mobile, so 3.0.0-beta.33 changes to platform-specific exports.

@1804davey We built a custom tool to codegen the raw jsi calls and TS types from annotating a kmp class. Works for us since we're pretty kmp heavy on the native side already

in react native, there are generally four(4) ways to add native code to your apps - raw dog it with JSI - use Turbomodules by the React Native team - use Expo modules by the Expo team - use Nitro modules by Marc/Margelo personally I think Nitro is the best regardless of if you're using expo/bare/ or @one__js :) this is because Nitro supports writing C++, Swift/Kotlin code without the hassle of Obj-c/Java present in something like Turbomodules(expo modules doesn't support C++ ) it also has great type-safety using a tool called nitrogen for converting typescript-defined types to their closest equivalents in native Swift/C++/Kotlin. lastly, it's the fastest of them all!

@JorgeCastilloPr They should probably have a disclaimer that it's super sped up

Maestro end to end testing is 🤯

@ChmalSzymon We're definitely interested in checking it out! We just built our own codegen tool for bridging kmp modules through jsi and having a tool to easily exercise the bridging code is very appealing

That was a good week for Harness. I'm curious to see how the graph will look next week, when the new testing capabilities drop 😉

@joreilly I've had my eye on meeseeks but it seems to have lost some steam. Probably worth taking a look at this. Thanks!

KMP WorkManager - Production-ready Kotlin Multiplatform library for scheduling and managing background tasks on Android and iOS with a unified API. github.com/brewkits/kmpwo… Haven't tried it yet but looks very interesting. Kudos as well for comprehensive docs provided.

@ipla03 Are signals meaningfully better than flows?

Just drafted a simple signals implementation in Kotlin to act as a building block to build a cross platform mobile framework Already working: - Stale/Ready notification mechanism to avoid re-running the same computation multiple times with stale data Still to go: - Batching signals updates