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

Developing Our First iOS App with React Native

code.hireart.com

Post reply on HN
Print view View original

61–70 of 135 posts

Re: Developing Our First iOS App with React Native

#61

Post by guelo »

warcher wrote: post #29

Truthfully, the language barriers are nothing next to the API barriers dealing with your platform of choice. I am probably giving away my age here, but there's very little that's new under the sun after you've tussled with... say one each of the big three language families. These being: Nasty old C (not going anywhere, ever. Deal with it.), modern scripting languages (Ruby, Python, et al) and the real deal functional…

I agree. Keeping up with the giant, buggy, constantly changing, platform API, as well as the whole ecosystem, from build tools to the app distribution and analytics, is by far the hardest part.

These abstractions on top of the platform might make it easier for quick prototypes if you don't have time to learn the language. But you'll lose some flexibility, power, visibility and community. After a while the initial speed benefits wear off since the language is a small part of the things you have to stay on top of, especially if the app takes off.

Re: Developing Our First iOS App with React Native

#62

Post by Apocryphon »

mostafaberg wrote: post #27
trollied wrote: post #9

Still, how do you get hired as a lead mobile dev without having and native platform skills? The entire development world has gone tits-up in the last 10 years. It's all about nonsense package management for JavaScript libraries (why can't I just include a .js off a cdn? npm? What the actual fuck?), and an endless stream of disparate components which are often ill-supported, or just plain ditched after they've had the…

HN gives makes me feel like I'm on a JS subreddit sometimes..

I used to call this place Hacker Node back in 2011. But I'm used to it now. If it wasn't JS, it'd just be another language/platform/library.

Re: Developing Our First iOS App with React Native

#63

Post by outworlder »

warcher wrote: post #29

Truthfully, the language barriers are nothing next to the API barriers dealing with your platform of choice. I am probably giving away my age here, but there's very little that's new under the sun after you've tussled with... say one each of the big three language families. These being: Nasty old C (not going anywhere, ever. Deal with it.), modern scripting languages (Ruby, Python, et al) and the real deal functional…

Yeah, I find the learning experience of any language to be like that, once you have a few under your belt.

Except Haskell. I can do the trivial stuff, but anything non-trivial is a chore to learn. It is not as if it has a learning curve, it has a learning brick wall that hits you very early on.

Re: Developing Our First iOS App with React Native

#66

Post by user8341116 »

mostafaberg wrote: post #20

Why is this on the top of HN ? Honestly, this is a bad thing, not a thing to show off. To quote the author: "We're web developers, not iOS developers." EXACTLY, don't bring your web tech into native platforms, learn to do it the right way or just hire someone who knows how to do it. Seeing things like that creeping into becoming a norm makes me cringe

This is literally just a paid ad for React on the front page. Gross.

Re: Developing Our First iOS App with React Native

#68

Post by tomjen3 »

warcher wrote: post #29

Truthfully, the language barriers are nothing next to the API barriers dealing with your platform of choice. I am probably giving away my age here, but there's very little that's new under the sun after you've tussled with... say one each of the big three language families. These being: Nasty old C (not going anywhere, ever. Deal with it.), modern scripting languages (Ruby, Python, et al) and the real deal functional…

That is one way to write the code, but if you do it that way you will never get the benefits of each language. Haskell and Lisp are both functional, but they way they are intended to be used are very different (example: if you don't use macros with lisp you are probably missing something. If you don't take advantage of lazy evaluation in Haskell you are also missing something).

Re: Developing Our First iOS App with React Native

#69

Post by tomjen3 »

mostafaberg wrote: post #20

Why is this on the top of HN ? Honestly, this is a bad thing, not a thing to show off. To quote the author: "We're web developers, not iOS developers." EXACTLY, don't bring your web tech into native platforms, learn to do it the right way or just hire someone who knows how to do it. Seeing things like that creeping into becoming a norm makes me cringe

It is on the top of HN because people find it interesting. People are interested in bringing different tech into native platforms to decrease how much it will cost them to develop the product and I for one don't really care if it is not how you are supposed to do "proper development". Once upon a time you weren't supposed to build servers out of commodity components, but it worked alright for google.

Re: Developing Our First iOS App with React Native

#70

Post by jdhawk »

user8341116 wrote: post #67

>Java? Objective-C? Swift?? I don't have time to learn things!!! Now let's start coding XDDDDDD Every cross platform mobile framework in a nutshell.

Its not the language thats hard, its the framework. Solution? Create a new framework?

Something is broken

Post reply on HN