3 ms·
You should read the article. You'd realize that you're not actually vindicated by its contents.
by dopamean 21d ago
You should read the article. You'd realize that you're not actually vindicated by its contents.
- hectdev 21d agoI read it. They chose native over shared. Hence vindicated.
- hermitwriter 21d agoDerp. Read it again.
- hectdev 21d agoShopify is moving its mobile apps from React Native back to native Swift and Kotlin. With the main cost of native gone, the benefits of staying close to platform APIs and first-party tooling win out. This has been my ethos. That native is better than shared.
- npunt 21d agoYour argument was you've argued your whole career for native. The article argues only very recently the cost equation has changed. Your argument reads like you are not taking into account the broader context or the passage of time.
- hectdev 21d agoI'll put it this way, my argument was pro native. And in the context of the article, if a large company had unlimited resources, they would choose native. I'm not discussing the business case for it, but the end result of it being the better option. It can be seen as "Shopify tried Reactive Native and left it behind the second they could after sinking resources into it for 6 years".
- hn993302 21d agoEveryone always knew native was better if dev cost weren't a factor
- fingerlocks 21d agoGo back in time and read the react-native vs native debates. Many react advocates claimed otherwise
- smackeyacky 21d agoTime and progress have overtaken them. At the time they were likely correct but I certainly wouldn’t bother with react native any more when the LLMs have gotten so good
- hn993302 21d agoWhat was the claimed advantage of react-native aside from ease of use?