Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Transition to React Native

blog.coinbase.com

Post reply on HN
Print view View original

111–120 of 221 posts

Re: Transition to React Native

#111

Post by intev »

EvilEy3 wrote: post #106
intev wrote: post #98

Earlier quoted context omitted.

I agree the current one is a major change but it's not mature yet. It hasn't stood the test of time. Twitter was built on RoR when that was the coolest new thing to build things on and Uber's booking engine was on Node.js when everything was being run on Node. I'm sure there's more I'm missing. .

You seem to be missing my point. Compose and SwiftUI are React of mobile world. React certainly stood the test of time.

That's to be seen. I very clearly remember when Angular first came out, that was clearly the way to move forward. People switched in droves. Then React came along and changed everything. React has also remained more popular than Angular has, but we didn't know that till years later. Some chose to remain in Angular (my old company) thinking it will blow over and we can swap to the next paradigm instead. Turned out React was flexible enough to last a while. Somehow you can perfectly see this is the React of mobile and not Angular?

Re: Transition to React Native

#112

Post by forgotpwd16 »

intev wrote: post #95
EvilEy3 wrote: post #80

Earlier quoted context omitted.

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.

It'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 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 wi…

>See https://insights.stackoverflow.com/survey/2020

What is this survey supposed to show?

Re: Transition to React Native

#113

Post by intev »

EvilEy3 wrote: post #101
intev wrote: post #93

Earlier quoted context omitted.

I call BS. I just downloaded it and it works fine. Literally every single one of your comments has it out for this transition. I trust my own experience and their data.

Try to create account, input some gibberish, see "something went wrong" dialog and close it. And define "fine" first. If you mean that it works, sure. But it works slower than truly native application, like Telegram.

By "fine" I mean it does what I expect it to, doesn't throw bizarre errors and hasn't crashed (so far). Could it be faster? Sure. Does it bother me? Not even the slightest. So many apps I use regularly run much slower than this.

Re: Transition to React Native

#114

Post by intev »

EvilEy3 wrote: post #105
intev wrote: post #96

Earlier quoted context omitted.

What has gotten you so upset about this transition? I don't understand. All your comments are so vicious with no backing. >You could've just said that you no longer want to invest in mobile talent. How does this even track? They had to retrain their engineers. I call complete BS with your app experience. I have a Redmi and the app works flawlessly. They seem to have internal data to prove it. They were under no oblig…

> All your comments are so vicious with no backing. I literally listed my experience with the app. And I didn't even create account yet. > How does this even track? They had to retrain their engineers. To leverage Web developers, right. > I call complete BS with your app experience. I have a Redmi and the app works flawlessly. Which Redmi? I'm testing on Xiaomi Mi A1. It probably works better on my Samsung S10. But t…

> I literally listed my experience with the app. And I didn't even create account yet.

That's not all you did. You implied they pay their employees very little, that they didn't do their research before making the switch and called the whole thing an "atrocity" which is heavy to the say the least. That's not an app review.

>Which Redmi? I'm testing on Xiaomi Mi A1. It probably works better on my Samsung S10. But then majority of people have phones closer to my Xiaomi.

I have a Redmi 8 (2019). Most people in the US have something similar to a low budget phone from 2017? I find that extremely difficult to believe. India, probably. US/UK etc? Highly unlikely.

> Because the blogpost makes it seem like there are only upsides to technology and the only downside is that it's not fit for brownfield.

Yes that is their experience so far. They wrote about it and have data to believe it. You don't have either except random anecdotal data and visions about the future.

> I had very bad experience with RN and give my opinion on tech. What's the problem?

Most of your claims don't have merit other than random anecdotal data which you are using to refuse their anecdotal data which is actually a lot less anecdotal that yours because they have many more developers and users.

Re: Transition to React Native

#115

Post by intev »

EvilEy3 wrote: post #99
intev wrote: post #95

Earlier quoted context omitted.

It'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 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 wi…

> It's still the most actively developed ecosystem for cross platform apps. Don't believe me? See 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 aff…

> 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.

Re: Transition to React Native

#116

Post by intev »

forgotpwd16 wrote: post #112
intev wrote: post #95

Earlier quoted context omitted.

It'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 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 wi…

>See https://insights.stackoverflow.com/survey/2020 What is this survey supposed to show?

To 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.

Re: Transition to React Native

#117

Post by rhodysurf »

geonic wrote: post #89
throw14082020 wrote: post #87

Earlier quoted context omitted.

Most teams don't hire a "mobile developer", they hire an Android developer, and/or iOS developer, and/or React Native developer, and/or Flutter Developer. So unfortunately it requires some commitment, don't do all of them at once! - React Native: Easiest to learn, good build tools/ developer experience, good amount of jobs already. Unfortunately, React Native is naturally intertwined with JS/ react, so you'll face is…

Could elaborate on why to avoid expo? I found it super easy to use when I dipped my toes into RN development. Also, what alternative are you suggesting?

I’ll give two reasons. First, code bloat, expo bundles allllll their default libraries along with your app when packaged for release. Second, is flexibility. The most powerful part of react native is that it displays native views and with expo you are only given the native functionality they bundle for you, you cannot create your own.

The alternative is to just not use expo and add libraries as you need them. Then you can do things like add widgets and watchOS functionality to your app on iOS using native code. Or create your own custom native views and plugins that bind to the native sdks, giving you an edge over other bland RN apps. I love RN but only when used correctly.

Re: Transition to React Native

#118

Post by rhodysurf »

throw14082020 wrote: post #87
vmception wrote: post #6

If I wanted to do android development again, I have no idea which skillset to optimize for React Native? Kotlin? An old version of Java that just got lambdas? Are we doing Model-View-Presenter (MVP) no matter which? Or are we still doing Massive-View-Controller (MVC backronym) Are there adequate networking, database ORM, and image loading libraries for all frameworks? Last time I interviewed for any mobile developmen…

Most teams don't hire a "mobile developer", they hire an Android developer, and/or iOS developer, and/or React Native developer, and/or Flutter Developer. So unfortunately it requires some commitment, don't do all of them at once! - React Native: Easiest to learn, good build tools/ developer experience, good amount of jobs already. Unfortunately, React Native is naturally intertwined with JS/ react, so you'll face is…

I very much disagree that Android is easier to learn and iOS. The iOS SDK is incredibly simple to get started with compared to android. Dealing with extensions on iOS is really hard, but creating apps involves so much less boilerplate than in android. XCode isn’t great, but I am not a IntelliJ Jetbrains fan at all, their IDEs are way too heavy for my taste.

Re: Transition to React Native

#119

Post by pixel_tracing »

intev wrote: post #111
EvilEy3 wrote: post #106

Earlier quoted context omitted.

You seem to be missing my point. Compose and SwiftUI are React of mobile world. React certainly stood the test of time.

That's to be seen. I very clearly remember when Angular first came out, that was clearly the way to move forward. People switched in droves. Then React came along and changed everything. React has also remained more popular than Angular has, but we didn't know that till years later. Some chose to remain in Angular (my old company) thinking it will blow over and we can swap to the next paradigm instead. Turned out Rea…

Unclear on what you mean here React will always be inferior to SwiftUI and Compose. All Apple has to do is release a new port of Javascript version 2 with limitations and boom goodbye React

Re: Transition to React Native

#120

Post by EvilEy3 »

intev wrote: post #111
EvilEy3 wrote: post #106

Earlier quoted context omitted.

You seem to be missing my point. Compose and SwiftUI are React of mobile world. React certainly stood the test of time.

That's to be seen. I very clearly remember when Angular first came out, that was clearly the way to move forward. People switched in droves. Then React came along and changed everything. React has also remained more popular than Angular has, but we didn't know that till years later. Some chose to remain in Angular (my old company) thinking it will blow over and we can swap to the next paradigm instead. Turned out Rea…

Compose is literally React. It has different execution model, but the same programming model.

Maybe you should first read about subject before arguing for the sake of arguing?

https://speakerdeck.com/lelandrichardson/react-meet-compose?...

Post reply on HN