3 ms·
You know what is dismissive? Switching to a lowest common denominator and offer subpar experience. This is what happens when you offer React Natives to users.
by EvilEy3 5y ago
You know what is dismissive? Switching to a lowest common denominator and offer subpar experience. This is what happens when you offer React Natives to users.
They dismissed advancements in native development and they'll pay the price the future.
It's literally laughable that they decided to transition to half dead tech when Compose and SwiftUI are ramping up.
- intev 5y agoIt's literally laughable that you call react native a half dead tech. It's still *the* most actively developed ecosystem for cross platform apps. Don't believe me? See https://insights.stackoverflow.com/survey/2020 https://insights.stackoverflow.com/survey/2020 Moving such a mature company's codebase to bleeding edge tech is one of the stupidest decisions you can make. Is there some price to be paid to be in the future? I'm sure there will be, as there will be with any non native platform. Whether is will be a deal breaker is to be seen.
- EvilEy3 5y ago> It's still the most actively developed ecosystem for cross platform apps. Don't believe me? See https://insights.stackoverflow.com/survey/2020 https://insights.stackoverflow.com/survey/2020 Riiiight, and quickly followed by Xamarin and Cordova. Lol. Of course it is not dead in terms of usage. It is more "dead" for anything complex. I'm looking from a perspective of a best experience, best performance and best integration. If your only reasoning is "we can't afford proper mobile developers" that's probably not the best pitch for a technical folk. Even Facebook, creators of React Native don't use it. > Moving such a mature company's codebase to bleeding edge tech is one of the stupidest decisions you can make. Is there some price to be paid to be in the future? I'm sure there will be, as there will be with any non native platform. Whether is will be a deal breaker is to be seen. Who says about moving now?
- intev 5y ago> Riiiight, and quickly followed by Xamarin and Cordova. Lol. I'm confused - is this meant to be a disbelief of the survey? "quickly followed by"? Are we seeing the same thing? Did you see the %s? It is significantly lower. Of course there are Xamarin and Cordova developers still. Especially in Asia. > Who says about moving now? So wait years and see how everything plays out? So basically you have no solution. Clearly the issues were pressing enough that they needed a more immediate solution. A solution they thought was worth re attempting despite its previous failures.
- EvilEy3 5y ago> I'm confused - is this meant to be a disbelief of the survey? "quickly followed by"? Are we seeing the same thing? Did you see the %s? It is significantly lower. Of course there are Xamarin and Cordova developers still. Especially in Asia. Oh, I'm sure there are many of them! Just as there are many Visual Basic developers, or people who do everything in Excel. > So wait years and see how everything plays out? So basically you have no solution. Clearly the issues were pressing enough that they needed a more immediate solution. A solution they thought was worth re attempting despite its previous failures. No, my solution to the problem would be to rewrite from scratch in native, without waiting for Compose/SwiftUI. But for some reason it is so much easier to justify rewrite in X, because if it was written in Y, than of course Y is to blame for our shitty practices and lack of developer culture. They neglected best practices, piled crap upon crap and somehow it is native toolkit that is to blame.
- intev 5y agoYea so your react native is dead argument is bs. You clarified it later saying you meant for complex projects but in another comment you claim that they're just a crypto dashboard. So which is it? Do they have a complex project (not a dashboard) and need something more than react native or they're a dashboard app and react native is fine? The things you say don't line up.\ > But for some reason it is so much easier to justify rewrite in X, because if it was written in Y, than of course Y is to blame for our shitty practices and lack of developer culture. They neglected best practices, piled crap upon crap and somehow it is native toolkit that is to blame. Is it really incomprehensible that there's a valid reason to rewrite in X? Now you claim they have shitty practices and no developer culture? What did coinbase do to you? Have you worked there? Did you see their "crap" code? If you don't have anything to back it up, I'll add it to your bs list.
- ec109685 5y ago> Even Facebook, creators of React Native don't use it. Yes they do. https://www.facebook.com/careers/v2/jobs/710998039655439/ https://www.facebook.com/careers/v2/jobs/710998039655439/ "Work closely with our PM and design teams to define feature specifications and build the next generation of products leveraging frameworks such as React & React Native" The top contributors are Facebook Engineers: https://github.com/facebook/react-native/graphs/contributors?from=2021-03-24&to=2021-05-15&type=c https://github.com/facebook/react-native/graphs/contributors...
- forgotpwd16 5y ago>See https://insights.stackoverflow.com/survey/2020 https://insights.stackoverflow.com/survey/2020 What is this survey supposed to show?
- intev 5y agoTo show how popular the framework is and that it is not "dead". Also to sure that it is not universally hated. 57.9% loved is not as good as the 68.8% of Flutter but it's not a huge margin.