New Architecture support (fabric)

[exploitJ]

I wonder if your library supports New Architecture(fabric)?

[gtokman]

I'm looking for help on this atm, I haven't done a conversion to fabric on a library yet.

[mak12]

Hey, would love to contribute here for fabric support.

[gtokman]

hey 👋🏽 @mak12 that would be awesome :)

[GorbunovV]

@gtokman Hello. I wanted to know if work is underway to add support for the new architecture?

[gtokman]

@GorbunovV not yet from our team. Our app (Candle) is a few iterations from migrating to NA to prioritize, but we would definitely land a PR from the community before that.

[tinker-dev-monk]

Hey, I've tried both iOS and Android in a fabric environment and it seems to work fine, so it shouldn't cause any issues when I build later?

[jbrodriguez]

this library supports new architecture (as per their docs) and also uses nuke/coil

duguyihou/react-native-turbo-image: Performant image Component for React Native

[gtokman]

It looks like a cool project, but I'd be careful using bc of the binary XCFrameworks included for iOS. This means it's not truly open-source and opens up a concern if there are malicious codes added, as there is no way to verify.

[duguyihou]

hi @jbrodriguez

Many thanks for mentioning our project. Currently TurboImage supports new architecture because of interop layer. The next step is to rewrite it in Fabric view with backward compat 😄

hi @gtokman

It looks like a cool project, but I'd be careful using bc of the binary XCFrameworks included for iOS. This means it's not truly open-source and opens up a concern if there are malicious codes added, as there is no way to verify.

• Nuke ships with precompiled XCFrameworks for projects that don't use SwiftPM, which is a trusted source. So we don't need to copy the whole source code of Nuke as a dependency.
• I can not find any information that help me know using XCFramework as dependency is not truly open-source, can you provide it? Thanks ❤️

[gtokman]

Here's a direct link by Apple.

When you add third-party binary SDKs to your target as XCFrameworks, the behaviors of those packages become part of the behavior of your product. An attacker who’s able to inject a compromised version of the SDK into your project could change your app’s behavior and cause security and privacy issues for your developers, testers, and people who use your product.

I commented that it's a tradeoff I would consider as a developer when using an open-source project. Open-source thrives on transparency + allowing anyone to inspect and verify the code. As Apple mentioned, a precompiled binary obscures the underlying implementation, making it impossible to audit for malicious code or unintended behavior.

[duguyihou]

Yes, I agree it is a tradeoff. People still can verify the code from Nuke