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
New Architecture is here
51–60 of 127 posts
Re: New Architecture is here
#52Re: New Architecture is here
#53At 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
#54When react-strict-dom is totally ready for prime time it's going to be a game changer and react native will become an absolute juggernaut.
Re: New Architecture is here
#55I 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
#56Re: New Architecture is here
#57I 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…
Congratulations! You've described the universal experience of using cross-platform frameworks. They can be great as long as you and your customers stay on their most well-trodden path. But as these frameworks grow and become more byzantine, and as your project requirements start reaching for more rarified features and your customers start using new and differing runtime platforms, maintenance overhead starts to domin…
But I still feel in the end that for many CRUD style apps it's worth it to deal with react native's problems, especially if you can also have significant code sharing with your web app.
If you're trying to build the next snapchat or tiktok you'd better go full native though.
Re: New Architecture is here
#58Is 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.
I love that you asked this question. As someone who has created a few react native applications in the past, non expo environments has felt as an afterthought. I hope the react native team will improve the documentation and encourage the native platform as well as the expo platform. Some of us don't want to be locked into yet another SaaS with questionable payment tiers - when building your own modules and publishing…
Can you expand on this? How does Expo prevent or make it harder for you to ship media- and VOIP-related features?
Re: New Architecture is here
#59At 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…
Such comments should really be directed at dang who keeps maintaining that there’s no data point to think that the state of discussions are declining. One way to address this might be to compute some relevance metrics using embeddings (they’re the new hotness after all) and downrank low relevance discussions. I assume it’d be especially effective for the “ads and JavaScript” discussions.
I would simply say a lot of contrarian viewpoints, regardless of merit, are downvoted into oblivion. Once you get hammered on something you simply had a different viewpoint on? Users tend to stop commenting for fear of reprisals. Your "karma" on here is not easy to obtain so when people downvote you simply for a differing opinion, it makes it less likely they will wade into a discussion again and find themselves on the wrong side of some Hacker News diva having a bad day.
This means you have a lot of people (like myself) simply opting out of a lot of discussions because if you're not on the right side, your comment will get downvoted immediately. There is no data point on people like myself, so there's no way to tell people that the quality on HN is declining, everything is just fine and normal when in reality, you have a lot of users who aren't engaging for fear of getting downvoted into oblivion.
Re: New Architecture is here
#60When they emerged, the mobile development scene was completely different than today.
Today, we have Swift UI and Compose, both are pretty solid. I'm not sure if it's the consensus amongst mobile developers, but I believe that on the mid/long run you will be better off - even if you write things twice. In terms of end user experience, developer experience, and in the business sense, everywhere.
Sure if you have an Flutter / RN app that has years of engineering efforts invested into it, go ahead and continue (duh), but I wouldn't start new apps with them.