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

201–210 of 221 posts

Re: Transition to React Native

#201

Post by pjmlp »

hardwaresofton wrote: post #190
mekkkkkk wrote: post #182

Earlier quoted context omitted.

What made you dislike Dart? I find it a highly inoffensive language.

In no particular order: - The type system was essentially like java but perhaps even worse -- in a world with Rust, Haskell, Julia, Kotlin, Scala, and even Golang this seemed egregious. - No algebraic data types (sum/union), - class-based inheritance - nullable values - using exceptions instead of errors-as-values approach. I know they worked hard on the language (rewrites are hard, there are some good talks on there…

Sony also a track record of letting developer communities down that aren't that relevant on their revenue stream, e.g.

- PS2Linux

- Linux on PS3

- Indie DevTooling for PSP

Re: Transition to React Native

#203

Post by robertlagrant »

Jare wrote: post #129
_fat_santa wrote: post #77

Earlier quoted context omitted.

I highly disagree that an expert RN dev also needs to be an expert mobile dev. Articles like these make it seem that react native development requires native knowledge but that simply isn’t the case. With almost all greenfield RN apps, 99.9% of the code is RN and only very specific feature are helped out by native code.

You don't need to be an expert in native to write a RN app. However, you need to be very capable in native to have a responsive, performant, smooth RN app, and to keep it that way for years. Large teams can afford to have a subset of platform devs and a large body of RN app devs to make this plan work (note: you now have 3 platforms: iOS, Android, and RN itself). Smaller teams will struggle. Most often, small teams w…

This is where Kotlin Multiplatform works well - you only need Android/Kotlin, and iOS/Swift skills. You save money where you can (e.g. shared code to do API calls / auth / calculations / etc etc) and still get the best-quality apps from the native code you're still writing.

Re: Transition to React Native

#204

Post by hardwaresofton »

pjmlp wrote: post #201
hardwaresofton wrote: post #190

Earlier quoted context omitted.

In no particular order: - The type system was essentially like java but perhaps even worse -- in a world with Rust, Haskell, Julia, Kotlin, Scala, and even Golang this seemed egregious. - No algebraic data types (sum/union), - class-based inheritance - nullable values - using exceptions instead of errors-as-values approach. I know they worked hard on the language (rewrites are hard, there are some good talks on there…

Sony also a track record of letting developer communities down that aren't that relevant on their revenue stream, e.g. - PS2Linux - Linux on PS3 - Indie DevTooling for PSP

I'd argue most companies do this, but do the bit where they never even embraced the developer communities in the first place.

The fact that those things were even allowed to exist is awesome, and the best thing I've seen out of MS on this front is Kinect. Not sure if Nintendo has done things that developer friendly.

Most companies are intent on making full on walled gardens.

Re: Transition to React Native

#206

Post by alexandr1us »

jpeter wrote: post #185
alexandr1us wrote: post #154

I want to write small review regarding replies on this link. I am working as an mobile engineer for more than 8 years now. I have worked on native iOS, Android, Xamarin, Unity, Titanium, Flutter and React Native. Long story short I have never been happier since I switched to React Native and Expo made everything so much better. I am not comparing it to native but I can compare it to Flutter. First of all Flutter has…

What was the worst framework? Xamarin?

Titanium was worse

Re: Transition to React Native

#207

Post by alexandr1us »

powerapple wrote: post #168
alexandr1us wrote: post #154

I want to write small review regarding replies on this link. I am working as an mobile engineer for more than 8 years now. I have worked on native iOS, Android, Xamarin, Unity, Titanium, Flutter and React Native. Long story short I have never been happier since I switched to React Native and Expo made everything so much better. I am not comparing it to native but I can compare it to Flutter. First of all Flutter has…

Thank you for the info. I am starting a project and was thinking choosing Flutter or React Native. I have used both Flutter and RN for some small toy projects. I really liked Flutter with fastlane. Does fastlane still work? Do people actually use Unity for apps? I am actually building an app for kids, Unity can be really interesting for me.

I used to use Unity for apps since it made perfect sense for simple game like apps

Re: Transition to React Native

#208

Post by mekkkkkk »

pixel_tracing wrote: post #196
mekkkkkk wrote: post #183

Earlier quoted context omitted.

Which native mobile engineering team?

The ones that were initially hired to work native Android / iOS? We’re they down sized? Re trained? Etc. and so on. Can you speak about the process around this and so on. I understand you want to give a positive image externally here, but I’m more interested in what struggles occurred and how you resolved it / did not resolve it.

Sorry, I'm not the OP. I just tried to be funny. As in "there's probably no such team anymore".

Re: Transition to React Native

#209

Post by pjmlp »

hardwaresofton wrote: post #204
pjmlp wrote: post #201

Earlier quoted context omitted.

Sony also a track record of letting developer communities down that aren't that relevant on their revenue stream, e.g. - PS2Linux - Linux on PS3 - Indie DevTooling for PSP

I'd argue most companies do this, but do the bit where they never even embraced the developer communities in the first place. The fact that those things were even allowed to exist is awesome, and the best thing I've seen out of MS on this front is Kinect. Not sure if Nintendo has done things that developer friendly. Most companies are intent on making full on walled gardens.

Depends on which idea you want to sell them, https://developer.nintendo.com/

Re: Transition to React Native

#210

Post by mekkkkkk »

hardwaresofton wrote: post #190
mekkkkkk wrote: post #182

Earlier quoted context omitted.

What made you dislike Dart? I find it a highly inoffensive language.

In no particular order: - The type system was essentially like java but perhaps even worse -- in a world with Rust, Haskell, Julia, Kotlin, Scala, and even Golang this seemed egregious. - No algebraic data types (sum/union), - class-based inheritance - nullable values - using exceptions instead of errors-as-values approach. I know they worked hard on the language (rewrites are hard, there are some good talks on there…

Thanks for the elaborate answer! You probably have a higher standard on programming languages than I do. I understand that Dart is a very basic language, and comparing it to something almost academic like Haskell will probably make it seem real primitive and stupid. Coming from mostly frontend/UI product dev in C#/Java/JS I've had a blast with it though.

I do agree that some common patterns are contrived (BLoC, json serialization via codegen, etc), but I'm not sure it's fair to criticize the language itself for this.

Also FWIW sound null safety is now the preferred way to write Dart (given your deps have adapted to it), so that part is hopefully solved.

Post reply on HN