Live data from Hacker News

Relicensing React, Jest, Flow, and Immutable.js

code.facebook.com

461–470 of 528 posts

Re: Relicensing React, Jest, Flow, and Immutable.js

#461

Earlier quoted context omitted.

I am also not a lawyer. But I don't think a "promise" is a legally enforceable concept.

I'm not a lawyer either, but the estoppel doctrine should make it enforceable.

This whole I'm not a lawyer business brings this to mind... https://pbs.twimg.com/media/DKF9KCcXkAA11ez.jpg

Re: Relicensing React, Jest, Flow, and Immutable.js

#462

Earlier quoted context omitted.

Please tell me more about commercial sales of GPL software. How could I make sure that people pay me for using my desktop app if it was GPL?

A common misconception is that under GPL all your code must be released to the public. This is not true. You only have to give code to the user after purchase. Now, it's true that the user could then upload your software to the public (under gpl), but many of the issues surrounding that (such as lost sales #) aren't as bad as people imagine they are, and in the foss world are generally made up for by high-maintainenc…

I feel like this works for some things, like Redhats core businesses for instance, as you noted. If I’m an indie software developer though and release say a tool for managing Wordpress sites or maybe I release an app that is like a crazy good bookmarks manager, how can I justify losing revenue when most users don’t care if the source is open and those who do probably won’t buy my product. Yet the inverse - one user getting that code and uploading it online - could damage me greatly?

How do you reconcile that

Re: Relicensing React, Jest, Flow, and Immutable.js

#463
post #425

Earlier quoted context omitted.

Synergy [1] https://symless.com/synergy [2] https://github.com/symless/synergy-core

That's only some "core" for the software, not the full software, which is kept proprietary. And even that could hurt their business if somebody used the core to build their own app for the same target market on top of it.

I wouldn't say about what available on GitHub today, but up until year ago all source code was included and they only sold precompiled binaries and support. Also I doubt they can really change anything about that because Synergy never required CLA and it's under GPLv2.

I pretty sure their "core" naming is just another way to promote usage of paid version, but you can still compile it yourself and easily remove all license checks.

Re: Relicensing React, Jest, Flow, and Immutable.js

#465

Earlier quoted context omitted.

Many things going forward will happen in reacts petri dish. Lots of ideas seeking to get consensus like the evolution of styles, animations, native performance, async scheduler, easy-to-create native renderers. Vue is nice and all, but it's rather complacent, catering to old Angular-like roots and web artefacts. If you believed the hype then Vue was supposed to be the be-all-end-all of frameworks, the reality of cour…

I don't understand the link. We don't get Vue from NPM. I assume others don't either. That implies to me that the numbers implied in that chart are inaccurate at best.

where do you get it?

Re: Relicensing React, Jest, Flow, and Immutable.js

#466
post #316

Earlier quoted context omitted.

Is there no similar penalty for intentionally foregoing due diligence specifically to avoid harsher penalties?

There is not. If you know the patent exists, you get higher (I think triple?) damages. If you don't, you don't. And you have no obligation to check. Example: There is a patent in the US on ordering food from a menu online. It's held by a NPE (aka, a patent troll), and they charge a fairly high license fee. Some people who offer online ordering to restaurants pay the license fee; others don't. If you don't pay, then y…

Good god how is that even patentable?? That's not at all novel.

Re: Relicensing React, Jest, Flow, and Immutable.js

#467

Thank you, Wordpress.[1] [1] https://ma.tt/2017/09/on-react-and-wordpress/

Thank them for what? I don't get it. It sounds to me that they just ran away from the problem. The problem in my eyes being software patents not the BSD+Patents license. But sure, thanks for being weenies.

Re: Relicensing React, Jest, Flow, and Immutable.js

#468

Earlier quoted context omitted.

A common misconception is that under GPL all your code must be released to the public. This is not true. You only have to give code to the user after purchase. Now, it's true that the user could then upload your software to the public (under gpl), but many of the issues surrounding that (such as lost sales #) aren't as bad as people imagine they are, and in the foss world are generally made up for by high-maintainenc…

Do you have an example of a commercially successful GPL desktop app?

https://www.knime.com/

Re: Relicensing React, Jest, Flow, and Immutable.js

#469

Earlier quoted context omitted.

That's not what I meant. 25% of sites on the Internet run WordPress. WordPress was rewriting its editor in React, but decided to switch away due to BSD+Patents.

Right so even then, its a bit weird to say that 25% of sites decided to not go with React, but actually 25% of sites (unknowingly) use software that decided not to go with React.

You're splitting hairs to reduce the significance of WP's stance.

Re: Relicensing React, Jest, Flow, and Immutable.js

#470
post #394

Earlier quoted context omitted.

No it doesn't; read the license again. It disarms you from being the aggressor; if FB comes after you, you keep your right to counter-sue while also keeping your license to use the software.

Yes it does, Them using patents that you don't grant them and you being unable to sue them for it is definitely putting the power in their hands.

Yes, that's exactly the point. It disarms people from fighting over patent nonsense. If you hate software patents you should love the bad + patents license.
Post reply on HN