Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New Architecture is here

reactnative.dev

Post reply on HN
Print view View original

31–40 of 127 posts

Re: New Architecture is here

#31

Post by slothtrop »

jonas21 wrote: post #22
DCH3416 wrote: post #16

Earlier quoted context omitted.

No? Most modern apps these days _are_ just web apps. Why does it need the overhead architecture of running full standalone applications when a web clip works just as well? Plus there's no need for updating. The problem at the time was multifaceted. The devices couldn't handle it, the network couldn't handle it, and webkit was still relatively limited. But it did work. https://9to5mac.com/2021/06/03/remembering-apples…

If that's the case, then why does nearly every company have a native app in addition to their website? Surely, they could save a lot of time and money by just not building and maintaining the app.

Native apps make more money, because of phone data. A lot of effort is now put into facilitating cross-platform builds, a wrapper/container around a glorified web app is among the easiest ways

Re: New Architecture is here

#32

Post by adolfojp »

At the time of writing this comment, we've got:

1 person talking about how they wish react native didn't exist

1 person asking about Capacitor

1 person complaining about Expo

1 person saying that they wouldn't use react native and recommending Kotlin Multiplatform instead

1 person complaining about the quality of the discussion (Me)

0 people talking about the new architecture

I still love Hacker News but the discussions are becoming increasingly pointless.

All that's missing is:

1 person complaining about the style in which the article was written

Re: New Architecture is here

#33

Post by mhammerc »

I have been working for the past four years exclusively on react-native apps and their backend API, from bootstrap to publishing, adding new features every few months and maintaining the apps.

It was a mixed experience. When I migrated to expo two years ago, many problems were solved but not all.

But I still encounters bugs and problems with many common dependencies. It is not uncommon to have bugs on certain Android brands, with the community on github reporting the bug but waiting months for it to be fixed.

iOS is by far better and more stable than Android.

Performance is great on iOS, but less great on Android.

Our apps are animation heavy using react-native-reanimated and react-native-skia. Everything went perfect on iOS but we had to remove some animations or simplify them on Android.

Upgrading your dependencies every four months will probably break something somewhere : deep links stop working, some animations stop working, or maybe it's another dependency from the JS world. Sometime the fix is easy, other time an issue with the regression can be found on Github, other time we have no data.

Overall I'd say react-native is perfectly servicable and is easy to learn for anyone, which is a big plus. I'd recommend react-native because it is easy, have a big JS ecosystem, but I am now on the Flutter side.

Re: New Architecture is here

#34

Post by rickhanlonii »

arijo wrote: post #29

Guys, help me understand these changes: Can I comprehend this as a new Virtual Native UI immutable tree running in native space? And react native mounts and updates basically synchronally updating this immutable tree and reconciliation being done in native space, dynamically updating the app layout?

Kind of. We already had a native UI tree running in native (the same way the browser has it's own internal representation of the DOM). The difference in this release is that we rewrote it in C++ and made it immutable. That means instead of having a different UI tree in each platform (one for iOS, one for Android, etc), we have one C++ tree that all platforms use. And since it's immutable, it's thread safe and we can read layout and commit it from different threads if needed.

Reconciliation is still done in React on the JS thread, similar to React DOM.

Re: New Architecture is here

#35

Post by pavlov »

adolfojp wrote: post #32

At the time of writing this comment, we've got: 1 person talking about how they wish react native didn't exist 1 person asking about Capacitor 1 person complaining about Expo 1 person saying that they wouldn't use react native and recommending Kotlin Multiplatform instead 1 person complaining about the quality of the discussion (Me) 0 people talking about the new architecture I still love Hacker News but the discussi…

You forget:

1 person complaining about the amount of JavaScript loaded just to display this one article

Re: New Architecture is here

#36

Post by mdgrech23 »

adolfojp wrote: post #32

At the time of writing this comment, we've got: 1 person talking about how they wish react native didn't exist 1 person asking about Capacitor 1 person complaining about Expo 1 person saying that they wouldn't use react native and recommending Kotlin Multiplatform instead 1 person complaining about the quality of the discussion (Me) 0 people talking about the new architecture I still love Hacker News but the discussi…

Reddit does a lot better of job bringing good relevant comments to the top.

Re: New Architecture is here

#37

Post by Zelphyr »

theThree wrote: post #26

I did a performance test last year, rendering thousands of views, and Flutter's rendering speed was 5 times faster than React Native. I wonder if this version will be improved after the update. Interestingly, I used React on the web to render the same number of views, and its speed was much faster than React Native.

I'm speaking out of turn here since I'm not a React Native developer but, it seems to me that it suffers from the penalty of having to use the JS bridge that neither Flutter nor web use.

Re: New Architecture is here

#38

Post by andy_ppp »

adolfojp wrote: post #32

At the time of writing this comment, we've got: 1 person talking about how they wish react native didn't exist 1 person asking about Capacitor 1 person complaining about Expo 1 person saying that they wouldn't use react native and recommending Kotlin Multiplatform instead 1 person complaining about the quality of the discussion (Me) 0 people talking about the new architecture I still love Hacker News but the discussi…

And you are complaining about the complaining. Great work.

EDIT: I’ve added to the problem which is ironic and just missed the delete button.

Re: New Architecture is here

#39

Post by tcoff91 »

ramesh31 wrote: post #2

Is there any sane way of using RN without locking into the Expo ecosystem? Last I checked it was a nightmare dealing with native dependencies otherwise.

Having used bare RN for 5 years, and recently started using Expo, there really is no reason to not use Expo at this point.

The native dependencies are 100% solved by prebuilds, CNG, and config plugins.

Re: New Architecture is here

#40

Post by adolfojp »

andy_ppp wrote: post #38
adolfojp wrote: post #32

At the time of writing this comment, we've got: 1 person talking about how they wish react native didn't exist 1 person asking about Capacitor 1 person complaining about Expo 1 person saying that they wouldn't use react native and recommending Kotlin Multiplatform instead 1 person complaining about the quality of the discussion (Me) 0 people talking about the new architecture I still love Hacker News but the discussi…

And you are complaining about the complaining. Great work. EDIT: I’ve added to the problem which is ironic and just missed the delete button.

That's literally point #5 of my comment. Didn't you read it?
Post reply on HN