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

281–290 of 318 posts

Re: Why I'm Not a React Native Developer

#281

Post by SomeCallMeTim »

wmil wrote: post #231
SomeCallMeTim wrote: post #38

Earlier quoted context omitted.

Exactly: Linting rules requiring semicolons should be considered a best practice. But I think TypeScript should also be considered a best practice, and between the two that would solve pretty much all of his complaints. Well, that and using "==" to compare to null, vs. "===" to compare to everything else. But the linters all can make that distinction as well. But he explicitly hates on linters in the article as well.…

For anyone else reading this in the future, I should mention that the ESLint 'no-unreachable' rule will catch this even if you don't require semicolons.

Good point!

Didn't say this explicitly, but TypeScript will, by default, prohibit unreachable code as well. [1]

[1] "allowUnreachableCode" defaults to false: https://www.typescriptlang.org/docs/handbook/compiler-option...

Re: Why I'm Not a React Native Developer

#282

Post by SomeCallMeTim »

gareim wrote: post #48
SomeCallMeTim wrote: post #35

Earlier quoted context omitted.

Angular 2 is pretty awesome and faster than React.

Source on that speed claim, please.

I can't find the benchmarks that I'd based my comments on to be honest, and I have to get back to work. :|

From what I remember, the final version of Angular 2 added a lot of performance, which pushed it ahead of the latest React in performance.

I did find this:

http://webscripts.softpedia.com/blog/recent-benchmark-shows-...

But the Auth0 benchmarks disagree and show React is faster:

https://auth0.com/blog/more-benchmarks-virtual-dom-vs-angula...

Angular 1 is terrible performance-wise; that much is certain.

Re: Why I'm Not a React Native Developer

#283

Post by qwertyuiop924 »

aurelianito wrote: post #279
tempodox wrote: post #176

Earlier quoted context omitted.

> ...an error doesn't have the potential to hand you a segfault. And that is a good thing why? So you don't realise there was an error and your app runs on in a corrupted state?

For starters, a huge set of security vulnerabilities are not possible. Ex: buffer overflow, double free, reading uninitialized memory.

Precisely. Don't write Application code in a systems language.

Re: Why I'm Not a React Native Developer

#284

Post by caub »

zghst wrote: post #267
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

Object.is(a,b) end of story

no, -Infinity is not Infinity

Re: Why I'm Not a React Native Developer

#285

Post by caub »

kuschku wrote: post #234
Arkanum wrote: post #224

Earlier quoted context omitted.

I'm not sure that's right. 1/0 is undefined NOT infinity, hence -1/0 is also undefined . So actually line 3 should evaluate as true.

NaN === NaN evaluates to false. That’s what happens here, not anything with Infinity.

just type them in your console instead of saying wrong things

Re: Why I'm Not a React Native Developer

#286

Post by [deleted] »

StyloBill wrote: post #250
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.

[deleted]

Re: Why I'm Not a React Native Developer

#287

Post by tboyd47 »

This article is beautiful.

I am not a React Native developer, but I am a React Web developer (not by choice). The author summed up my feelings about React and JS in general so eloquently. The Swamp Castle and Freedom from Digging bits were so on point.

I am betting that my comment will get buried in the bottom of the comment avalanche, but if the author is reading, thank you for making my day!

Re: Why I'm Not a React Native Developer

#288

Post by wtbob »

qwertyuiop924 wrote: post #240
wtbob wrote: post #230

Earlier quoted context omitted.

Lisp, though, does have types.

All languages have types. Lisp, however, and particularly the versions that those people worked with, are dynamically typed, like Javascript. Unlike JS, they aren't weakly typed, but that's not the point. To say nothing of Ruby and Python, for which there are also programmers on that list.

Common Lisp compilers may implement static typing. The default type is T, though — but with declarations, a compiler can enforce anything the programmer declares or it infers.

Re: Why I'm Not a React Native Developer

#289

Post by DiThi »

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…

> Apple's Developer terms 3.3.2 and 3.3.3

Where can I find them?

Re: Why I'm Not a React Native Developer

#290

Post by qwertyuiop924 »

wtbob wrote: post #288
qwertyuiop924 wrote: post #240

Earlier quoted context omitted.

All languages have types. Lisp, however, and particularly the versions that those people worked with, are dynamically typed, like Javascript. Unlike JS, they aren't weakly typed, but that's not the point. To say nothing of Ruby and Python, for which there are also programmers on that list.

Common Lisp compilers may implement static typing. The default type is T, though — but with declarations, a compiler can enforce anything the programmer declares or it infers.

Most of those people either worked with MACLisp, or dynamically typed Scheme.
Post reply on HN