Ya, probably. But that's an easy fix: just don't contribute. You can still use it.
-
-
when you use [INSERT WEBSITE HERE] you're participating in a scheme to mitigate legal risks that's how ToCs work.
-
Anyway, I fail to see how the patent grant is in any way applicable to me if I don't use patents and want to discourage their use.
-
If you don't have your own patents, there's really nothing to see here.
-
Unless you care about the stability and long-term viability of the open source ecosystem.
-
As you said, Facebook is deciding to put its own interests above the community. Disingenuous to tell the community "nothing to see here"
-
I'm referring to the immediate, practical, micro-level Q of: how does the license affect *me*. If you don't have patents, it really doesn't.
-
Right, but maybe if you don't have patents (and therefore are a little guy) you care about the long term big picture.
End of conversation
New conversation -
-
-
FB holds tons of patents to discourage you from suing (or face countersuit). They just won't allow you to use React as shield if you sue 1st
-
Apache is more 'balanced' but risks of parties are not equal here. FB is much more likely to be sued by you than you are to be sued by them.
End of conversation
New conversation -
-
-
Main reason why I probably won't contribute code to any FB OSS project. I don't think as a non FB employee I should strengthen their power
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Well if you use Ember and sue FB for patent infringment their patents will probably stil apply to Ember too, so no real difference there..
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.