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

Why I'm Not a React Native Developer

arielelkin.github.io

Post reply on HN
Print view View original

241–250 of 318 posts

Re: Why I'm Not a React Native Developer

#241

Post by threepipeproblm »

cloverich wrote: post #236
threepipeproblm wrote: post #226

Earlier quoted context omitted.

Then why don't you drink this glass of 70% orange juice and 30% motor oil, since by your definition it's "simply orange juice". I sure am glad to know about the patent considerations in this simple criticism in this JavaScript, as I've decided not to use React because of them.

You should read @pluma's explanation of the patent grant. I think its purely a misconception that's unfortunately been regularly repeated. > Then why don't you drink this glass of 70% orange juice and 30% motor oil, since by your definition it's "simply orange juice". I think a more proper correlation of your analogy vs OP's argument would be if you held it up and claims "why I won't be putting this motor oil into my…

Not sure I follow your orange juice / motor oil rebuttal but I'm going to focus on the more substantive portion of this interchange...

It's purely a misconception in the same way that 30% motor oil is pure orange juice -- which is to say, it's not a misconception, by my reading. I wonder what my IP laywer would say about it, will post if I decide to ask.

Unless I am looking at the wrong comment, @pluma's explanation is just that it's not a problem as long as you don't sue Facebook. But this is equivalent to saying that as long as you give up your only recourse in the event FB violates your IP, you'll be fine. To me it seems like a mentality that makes sense primarily if a person doesn't ever expect to do anything worth patenting, or doesn't ever plan on patenting for some other reason. Don't sell yourself short.

Re: Why I'm Not a React Native Developer

#242

Post by Sagiri »

> There is no mechanism for you to mark a function as potentially crashing your teammate’s code or for specifying how to process an exception.

Maybe I'm misinterpreting this, but is the author actually advocating for Java-style checked exceptions? I can't even remember the last time I heard somebody say something positive about them (other than just now, possibly).

Re: Why I'm Not a React Native Developer

#243

Post by qwertyuiop924 »

pluma wrote: post #232
qwertyuiop924 wrote: post #63

Earlier quoted context omitted.

Because it gives Facebook legal leverage over your company.

You mean unlike every company that is behind any other project you are relying on that doesn't come with an explicit patent grant? In other words you have no MIT or BSD licensed dependencies, or in fact no open source dependencies that don't either come with an explicit non-revocable patent grant and aren't licensed under Apache 2.0, GPLv3 or MPL 2.0 (all of which by the way still terminate the patent grant if you su…

True, but it give Facebook more legal leverage over you, arguably, and Facebook is more likely to abuse that power than a loose collection of open-source programmers, or a smaller, less wealthy company that doesn't have its tendrils everywhere.

Re: Why I'm Not a React Native Developer

#244

Post by coldtea »

ulisesrmzroche wrote: post #235
coldtea wrote: post #206

Earlier quoted context omitted.

70% of the content is not necessarily "the most important part of the content". 2 minutes in a 5 minute animation short are the credits.

You know theres no 5 minute animation shorts with 2 minute credits in existence.

If you ever go to a short film festival, animation or not, you'd be surprised.

Here's a 2:18 animation with 1:06 credits -- way more than the ratio I gave: https://www.youtube.com/watch?v=8ZRLlyxvr6E

Credits --crew members, voice talent, sponsors, thanks, etc-- can rise almost linearly with the length of an animation, and even more so with increases in its production value.

A 5 minute short can have almost the same team size as a feature animation (which requires > 2 minute credits). The fact that they'll be employed for shorter time doesn't mean they don't get their names on the credits.

Re: Why I'm Not a React Native Developer

#246

Post by iron_ball »

crimsonalucard wrote: post #185
vikeri wrote: post #152

Earlier quoted context omitted.

You can build RN apps in ClojureScript and, voila: You rarely have to touch JS. Edit (it's not without its flaws though): https://youtu.be/6IYm34nDL64

Did you read the article? Compiling to JS is an issue that is addressed.

Only barely; he includes it as the middle of a chain of hacks that highlight, not remedy, the deficiencies of Javascript.

Re: Why I'm Not a React Native Developer

#248

Post by jjuel »

jondot wrote: post #151

I'm the author of http://programmingreactnative.com , maintain the https://github.com/jondot/awesome-react-native list and built some other tools and libraries for React Native, along with a few apps. Obviously the conclusion that follows is that I think React Native is going to be a revolution for mobile development. Not only will it succeed, it will get copied, and you'll have many variants of the same like-minded…

So we will have many variants? Does sound like a classic JavaScript thing to have many frameworks that do the same thing. Reminds me of this: https://xkcd.com/927/

Re: Why I'm Not a React Native Developer

#249

Post by steego »

pzh wrote: post #92
steego wrote: post #25

Earlier quoted context omitted.

I prefer statically-typed languages too, but this is easily solved by using something TypeScript or Flow.

Yeah, but why use another patch on top of a patch where there are modern type-safe languages like Swift. JS has its uses, but it's difficult to debug, doesn't take advantage of all the advances in modern languages design that help prevent whole classes of bugs, and carries a lot of baggage. The only benefit would be universal app development, but even then Xamarin seems like a better choice.

> Yeah, but why use another patch on top of a patch where there are modern type-safe languages like Swift.

The JavaScript toolchain is more than good enough to build the kinds of applications that React Native targets. Most of these applications aren't stellar apps that require critical performance or rigorous type checking, they're just dumb front-ends to REST endpoints. If you're going to build an awesome app, then use better tools.

The reason I would use React over Xamarin is simple: Speed of training and development. I can hire, train and get a React developer up and running and building proof-of-concepts a lot quicker than on Xamarin.

Re: Why I'm Not a React Native Developer

#250

Post by StyloBill »

caub wrote: post #204

var a = 0; var b = -0; console.log(a === b) // true console.log(1/a === 1/b) // false That's perfect math you mean, of course -Infinity != Infinity, what did you expect? I think you should rather think harder, learn math possibly, and your 'safety' problems with arrays are not problems at all, it's the opposite for other people

> I think you should rather think harder, learn math possibly

Oh the irony, when stating that 1/0 = infinity. If you'd learn maths yourself, you'd know that 1/0 is undefined.

Post reply on HN