3 ms·
Yes, AI have changed the game, and now you can build and maintain two separate projects in Swift & Kotlin instead of one on React
by railka 24d ago
Yes, AI have changed the game, and now you can build and maintain two separate projects in Swift & Kotlin instead of one on React
- deleted 24d ago[deleted]
- kamaal 23d agoIf AI can make any language do anything, why move away from React Native ? What you could do with Kotlin/Swift you can do with React Native as well. This just feels like internal factions wanting their own teams, and owning their respective politics, than a discussion on Merit.
- lysium 23d agoOthers mention quicker startup of the app, more native-look, less head-ache w/ RN.
- mcosta 23d ago> What you could do with Kotlin/Swift you can do with React Native as well. In theory yes, in practice no. I mean, in theory you can do it in mips ASM and ship QEMU along with the app, in practice it makes no sense.
- liamgm 23d agoNative is fast , no extra layer , the problem is maintaining on every native platform your app available. And AI tooling can handle that efficiently today , not way back then. The problem with xplat is they add extra layer on top of platform native. - React native and similar, add extra js runtime engine. - Flutter and Kotlin MP add extra skia graphics engine. - Skiptools add extra swift runtime - Cordova adn similar add extra browser engine - Etc
- simondotau 23d ago“One React app vs two native apps” is a false comparison. A sufficiently polished React Native app still means two platforms to tune, test, debug, ship, and maintain. It gives you the appearance of efficiency and uniformity, but much of the complexity is just moved elsewhere… including, sometimes, to resource consumption on users’ devices.