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

311–318 of 318 posts

Re: Why I'm Not a React Native Developer

#311

Post by Noseshine »

pluma wrote: post #292
michel-slm wrote: post #266

Earlier quoted context omitted.

The patent retaliation is more broad than the provision in the Apache license though, which basically only revoke the patent grants for a specific work if you sue over patent infringement in the same work. http://en.swpat.org/wiki/Patent_clauses_in_software_licences...

Yes, I actually wrote a paragraph on Apache/GPL/MPL patent grants which I deleted before submitting because it's really not relevant to the argument. React, like most JS projects, is licensed under an MIT/BSD style license (they're too similar to be worth the distinction in this context). The alternative to having the FB patent grant wouldn't be to have the Apache 2.0 patent grant. It would be having no patent grant,…

So I'm suddenly very interested after hearing about this issue. The discussion always seems to be about Facebook suing me, assuming all is fine because why would I sue them?

The problem is the startup I work for relies on patents for a big part. And if we use any Facebook stuff, which I actually wanted to do as the main developer (react and react-native), they can use our stuff without caring about our patents! Because we can't sue them!

So basically, with that license Facebook on the one hand protects itself against patent trolls. Good, fine.

On the other hand though they grant themselves the right to use any patent of any company that uses their products, because you can't sue them any more! No? That's how I read it after having read a lot of discussions, none of which talk about that major issue, because for most people in this discussion defending their own patent(s) against Facebook is not an issue, so the discussion is very heavily one-sided towards people who don't have that problem.

Re: Why I'm Not a React Native Developer

#312

Post by bbcbasic »

threepipeproblm wrote: post #227
franciscop wrote: post #159

Please what kind of programmer would ever do this? if (weAreConnected === true) { this.setState({ isConnected: true }) } else { this.setState({ isConnected: false }) } That is just verbose unnecessarily: this.setState({ isConnected: weAreConnected }); And probably not so popular, but this: var color; if (this.state.isConnected) { color = 'green' } else { color = 'red' } Would be simplified often to: var color = this.…

Before 1900 Frege pointed out that we don't need to say, "The sea is salty is true"; we can just say "The sea is salty". A century later it still hasn't sunk in.

That's syntax sugar in the English language

Re: Why I'm Not a React Native Developer

#313

Post by pier25 »

gagege wrote: post #299
pier25 wrote: post #15

Earlier quoted context omitted.

In that case it would probably make more sense to just use NativeScript instead of React Native. https://www.nativescript.org/

I'll happily avoid anything made by Telerik for the rest of my life, thanks though!

Why is that?

Re: Why I'm Not a React Native Developer

#314

Post by ziziyO »

christocracy wrote: post #194
ziziyO wrote: post #111

Earlier quoted context omitted.

Anything where you need to stay alive in the background and periodically do something.

Utterly false. Staying alive has nothing to do with React Native or Cordova or any particular framework. It's about implementing the native APIs that allow that behaviour. I'm the author of a couple of modules that allow your RN app to operate in the background: https://github.com/transistorsoft/react-native-background-fe... https://github.com/transistorsoft/react-native-background-ge... Both of these modules were po…

Thank you for linking those modules. I'm in the early stages of an app that will benefit from that functionality and admittedly my knowledge is based off of the first google result of a search for "react native background worker/task" (http://stackoverflow.com/questions/35376690/how-can-i-run-ba...). Which of course makes me an expert on the subject in this day and age.

Re: Why I'm Not a React Native Developer

#315

Post by tempodox »

qwertyuiop924 wrote: post #195
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?

If you segfault, that's not because your state is corrupt. Not usually, anyways. Typically, you'll segfault from a use-after-free error or similar.

How else would you define corrupted state than “losing track of the objects in your app”? Not crashing as a consequence hardly makes it better.

Re: Why I'm Not a React Native Developer

#316

Post by pluma »

Noseshine wrote: post #311
pluma wrote: post #292

Earlier quoted context omitted.

Yes, I actually wrote a paragraph on Apache/GPL/MPL patent grants which I deleted before submitting because it's really not relevant to the argument. React, like most JS projects, is licensed under an MIT/BSD style license (they're too similar to be worth the distinction in this context). The alternative to having the FB patent grant wouldn't be to have the Apache 2.0 patent grant. It would be having no patent grant,…

So I'm suddenly very interested after hearing about this issue. The discussion always seems to be about Facebook suing me, assuming all is fine because why would I sue them? The problem is the startup I work for relies on patents for a big part. And if we use any Facebook stuff, which I actually wanted to do as the main developer (react and react-native), they can use our stuff without caring about our patents! Becau…

No. Patents don't care about code.

If FB has patents that cover parts of React, the same patents also cover similar parts in other projects, including your own.

By using React you prevent FB from using those patents against you within the project in which you use React instead of your own analogous code.

They can enforce their patents against you if you infringe on them in your code. They can't enforce their patents against you if you infringe on them by using React.

This is a protection you only get by using React. And it's the only thing that changes if you sue them over patents.

The only difference is that if you don't use React, depending on the exact patents, they might not be able to determine you are infringing on their patents without looking at your code (whereas if you use React they know which of their patents cover React).

But as I said, this "drawback" really pales in comparison to the very real risk of infringing on patents without even using React in the first place. Facebook might hold the patent for some ubiquitous aspect of your application and they could still sue you over that if they want to at any moment.

That said, if you run a software company and intend to sue Facebook over patents, you better believe that they have an arsenal that can take you off the market for good if they want to.

Besides, why would you want to use open source software created, maintained and sponsored by a company you're planning to sue?

Re: Why I'm Not a React Native Developer

#318

Post by pka »

bbcbasic wrote: post #294
pka wrote: post #219

Earlier quoted context omitted.

Elm's type systems is really constrained compared to PureScript's. It's great for people coming from JavaScript, but not so much for those coming from Haskell. Also, you still need FFI in Elm. elm-lang/virtual-dom is basically just a wrapper around the native virtual-dom library. Also, afaik there's nothing like react native for virtual-dom.

I was under the impression that Elm rolls it's own virtual-dom?

iirc they scrapped that in favor of virtual-dom a long time ago.
Post reply on HN