Project Catalyst. Does it truly deprecates this RN fork? about react-native-macos HOT 4 CLOSED

I think yes, Catalyst + RN is the future, and this project is effectively dead. Eventually macOS 10.15 will get a good adoption, and community will come with pretty good solutions for all edge cases.

from react-native-macos.

Deprecating this project seems odd to me. To my knowledge, Catalyst is about making it easy to port UIKit-based apps to macOS — it's literally UIKit for Mac. That's not the same as having a React paradigm for native AppKit controls. SwiftUI is close, but that's macOS 10.15+ only and, you know, not Javascript.

from react-native-macos.

On the one hand you're right — 10.15 is quite a heavy and indeed limiting requirement, and desktop UI is so much more than just UIKit for iPad (Catalyst) now. But on the other hand, let's face it, the core value react-native-macos is (or at least was 3 years ago) the engine itself, the ability to run React Native on macOS, using the same View, Text and other primitives. Which never worked well, due to limitations of AppKit. And the engine always way behind the React Native. But when you need something truly native and unique you always ended up writing a bunch of untrivial Objective-C (NSSplitView, text editors, etc., etc.)

Few UI wrappers around AppKit controls and APIs probably and hopefully can be just npm libraries now, since Catalyst allows to use AppKit from UIKit app.

Anyway, you're right, a word "deprecated" probably too much, there are use cases and React Native big refactoring gives hope that there is a solution to solve current react-native-macos problems. I removed "deprecated" and will add a more detailed note to README later after some experimenting.

from react-native-macos.

There's a PR

facebook/react-native#25427

from react-native-macos.