3 ms·
They specifically say in the post how React Native was the correct decision and that it worked well for them. Now it's a different situation as implementation
by user43928 22d ago
They specifically say in the post how React Native was the correct decision and that it worked well for them.
Now it's a different situation as implementation has become incredibly cheap.
- nielsbot 22d ago> worked well for them yeah because they don't care about a top notch user experience.
- hectdev 22d agoNot sure why someone would say it was a wrong decision. Why would they even need to do this if LLMs make coding easier. They are likely chasing the things I advocate for: direct access to latest APIs from each platform, platform specific UI, UI that behaves correctly on each platform without chasing down edge case solutions (also said as ui that looks and feels "right"), and a bonus of separate developer pool to hire from that knows the ins and outs of the platform without needing to hire a developer to know all three- react, iOS, and Android.
- throwaway27448 22d ago> Not sure why someone would say it was a wrong decision. Writing almost anything with javascript sucks ass to begin with. Writing native code with it is even more painful. Most javascript engines don't even have any decent model of parallelism. It takes zero imagination to see the problem here
- willsmith72 22d agohow much parallelism are you writing in your frontends?
- cloudfudge 22d agoThe problem with everything being single threaded isn't so much that you want to do a lot of parallel processing, but that you don't want to have the occasional fat loop cause the whole engine to start stuttering. If you want butter smooth scrolling while there's (for example) a lot of dynamic content moving around, you want very precise control of the threading so you can get the gnarly stuff done without causing hitches that don't feel right.
- user43928 22d agoThe browser, iOS, and Android all use a main thread separate from the thread responsible for scrolling animations. However, I think it's true that controlling threading in order to perform gnarly work in a separate thread is more ergonomic on mobile than in JS/React. You'd need to create a Promise that wraps a Web Worker, which would be an unusual thing to use. I don't think most apps need such control over threading in the browser.
- deleted 22d ago[deleted]
- throwaway27448 22d agoIf you care about smooth interactions, the browser even in 2026 is not the most straightforward route, nor the route any reasonable small company takes.
- hectdev 22d agoI mean, why would they admit to it being the wrong decision. Its a business.
- simonhamp 22d agoWhy would they need to worry about hiring for specific skills at all? As AI progresses, isn't the only skill that matters that you can drive it effectively (which encompasses testing and review) without needing oversight?
- gbalduzzi 22d agoBecause we are not there yet and you can't oversee something you don't know
- myko 22d agoYeah they do say that but as someone who has worked on native apps / RN for most of my career I think that is bullshit. They're not going to come out with a mea culpa owning that, this is as close as it gets.