technology

23815 readers

103 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.

founded 4 years ago

MODERATORS

[email protected]

120

Amazing (hexbear.net)

submitted 3 days ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 3 days ago

There’s definitely overhead to spinning up and running a JS interpreter (although it uses Hermes instead of V8, which helps) as well as communicating between JS and the native layer. I think the extent to which that stuff results in bad performance on its own is greatly exaggerated and is acceptable for a lot of use cases.

For the extra effort of learning how to optimize RN code, you get the benefits of:

not maintaining 3 codebases to deploy to iOS, Android, and the web
transferable knowledge if you have a lot of JS and/or React devs who don’t know the languages for native dev
OTA updates, meaning you don’t need Google and Apple’s approval every single time you wanna change styling on a button or fix a bug and your users can’t remain on ancient buggy versions forever

I’d say when dev resources are limited, React Native is a good choice. Was it a good choice for Microsoft? Seems like the answer is no, but that could easily be the result of bad org charts just as much as the failure of individual devs.

As far as vibe coding goes, I was very happy with it right up until I wasn’t. I hit the same “this is a mess I’d better rewrite it” wall I always do with side projects except I hit it faster. At work I’ve found AI useful for speeding up monotonous tasks, but I’ve never had luck with just letting it fly and not giving the code a close review as soon as it’s generated. Prompting AI to fix a bug it created seems to create more bugs just as often.