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

React Native at Instagram

engineering.instagram.com

Post reply on HN
Print view View original

151–160 of 238 posts

Re: React Native at Instagram

#151

Post by crispytx »

iamleppert wrote: post #53

They probably traded a really nice iOS codebase that had been maintained and improved upon for something that is going to end up with tons of special cases for when the UI is running on iOS/Android etc and make it incredibly difficult to test, reason about. Instead of improving the code on each respective platform, you end up with an inbred red-headed step child that shares the limitations and thorns of each, all smu…

I've never used React Native, but I have done a lot of messing around with Apache Cordova / PhoneGap. From my experience, you're probably better off just developing your apps the "standard way" with Android Studio or xcode. I'm sure React Native doesn't have the exact same problems as PhoneGap, but I bet there are some problems. If there weren't any problems, the iOS and Android codebases would be nearly identical. But that's just my opinion... man.

Re: React Native at Instagram

#152

Post by therealasdf »

hota_mazi wrote: post #126
40acres wrote: post #6

I didn't know what single/multi-dex means so i looked it up. Android application (APK) files contain executable bytecode files in the form of Dalvik Executable (DEX) files, which contain the compiled code used to run your app. The Dalvik Executable specification limits the total number of methods that can be referenced within a single DEX file to 65,536, including Android framework methods, library methods, and metho…

There is no practical difference between single and multidex. Recent versions of Android are even better at creating these dex files effectively so users won't even notice the difference. Most of these methods are typically contributed by dependencies, not by the app itself.

Exactly, the only difference developers might notice is slower build times.

Re: React Native at Instagram

#153

Post by bitmapbrother »

pjmlp wrote: post #149
bitmapbrother wrote: post #124

Earlier quoted context omitted.

Thanks for the correction. Here's a transcript from the Android Developer podcast, courtesy of http://blog.osom.info/2014/10/multi-dex-to-rescue-from-infam... , talking about the issue with an Android engineer: >Tor: So [regarding] the infamous 64k method [issue].. I understand that it is a dex file format limitation.. which is a short integer. Do you have plans to address this somehow, by either change the dex forma…

Available on 0.x% of devices, thanks to them not forcing OEMs to update as part of Play Store contract.

Yeah, why they don't enforce this is baffling. I can give them a break for letting their OEM's take their time with OS updates, but not requiring their OEM's to issue security patches is negligent.

Re: React Native at Instagram

#154

Post by kartickv »

pjmlp wrote: post #148
kartickv wrote: post #125

Earlier quoted context omitted.

So why can't Google create a new version of the dex format, update Android Studio to generate it, and update the store to accept and distribute it to new devices? Seems easy enough for Google to be able to do.

Because of their clever idea of not forcing OEMs to update devices, almost no one will get that.

New phones will get it. Surely you're not arguing that Google shouldn't make any improvements to core Android because of the update situation?

Re: React Native at Instagram

#155

Post by izacus »

bitmapbrother wrote: post #153
pjmlp wrote: post #149

Earlier quoted context omitted.

Available on 0.x% of devices, thanks to them not forcing OEMs to update as part of Play Store contract.

Yeah, why they don't enforce this is baffling. I can give them a break for letting their OEM's take their time with OS updates, but not requiring their OEM's to issue security patches is negligent.

Microsoft enforced that and OEMs decided they'd rather build Android phones than Windows Phone ones. The rest is history.

Re: React Native at Instagram

#156

Post by pjmlp »

kartickv wrote: post #154
pjmlp wrote: post #148

Earlier quoted context omitted.

Because of their clever idea of not forcing OEMs to update devices, almost no one will get that.

New phones will get it. Surely you're not arguing that Google shouldn't make any improvements to core Android because of the update situation?

No, I am arguing that Google doesn't have the guts to improve the situation.

Most people around the world are on pre-paid, not contracts, and they only update their devices when the current one dies.

Even now, the majority of the devices being sold on the 300 € border are Android 5 or 6, with no planned upgrade to 7.

Re: React Native at Instagram

#157

Post by pjmlp »

izacus wrote: post #155
bitmapbrother wrote: post #153

Earlier quoted context omitted.

Yeah, why they don't enforce this is baffling. I can give them a break for letting their OEM's take their time with OS updates, but not requiring their OEM's to issue security patches is negligent.

Microsoft enforced that and OEMs decided they'd rather build Android phones than Windows Phone ones. The rest is history.

I think having an OS available for free was more relevant.

Re: React Native at Instagram

#158

Post by mnkypete »

lewisl9029 wrote: post #132

Has anyone tried using the React Native plugin for Windows [1] in a non-trivial app yet? I'd love to hear what experiences people have had with it, and if there's anything to watch out for coming from the RN Android/iOS camps. Any open source apps that makes use of React Native for Windows that you can point me to would be super helpful as well. [1] https://github.com/ReactWindows/react-native-windows

I mean, the Instagram App is also available on Windows, with almost all features as the iOS/Android counterparts. So I'm not sure, maybe they are already using that as well?

Re: React Native at Instagram

#159

Post by lenkite »

LeoNatan25 wrote: post #115
bennyg wrote: post #105

Earlier quoted context omitted.

Thanks for pointing that out, forgot my old site was still in the profile. What do you mean by feds? That's still a very confusing statement. Switched off of Xamarin about 8 months ago and haven't looked back. My organization had a ton of problems with Xamarin, without honestly that much gain at all. We still needed specific devs for Android and iOS. Sharing component and state code has been an absolute boon in produ…

Let me explain the "fed" thing. React Native's number one "feature" is that web developers are able to join in development, or even start a "native" app where it would not have been possible before due to no native development teams. In the web dev world, "fed" /front end developer/ is usually the term for the front end web developers - this is what I meant. (While iOS and Android is also front end, it seems "fed" is…

So, a backend developer would be a 'bed'. I can see how that goes..

Re: React Native at Instagram

#160

Post by MichaelGG »

pjmlp wrote: post #157
izacus wrote: post #155

Earlier quoted context omitted.

Microsoft enforced that and OEMs decided they'd rather build Android phones than Windows Phone ones. The rest is history.

I think having an OS available for free was more relevant.

Yeah, it's not like Samsung can go make iOS phones. And I highly doubt any of these hardware OEMs could possibly pull off a software project that doesn't suck, let alone a whole OS and dev ecosystem.
Post reply on HN