241–250 of 391 posts
Finally, people are beginning to realize the insanity of this entire PATENTS file situation! When I first brought up how misguided people were for embracing React and projects with this license, I was downvoted to hell on HN. But really, everyone, THINK ABOUT IT. This is a company that glorifies and celebrates IP theft from others, and lionizes their employees who successfully clone others’ projects. They’ve built th…
Earlier quoted context omitted.
On purely copyright grounds, any BSD licensed code can be relicensed as Apache 2.0 code. And the patent grant was solely from Facebook so it can be modified at their discretion.
This is incorrect. Here's the full text of BSD license: Copyright (c) 2011 The LevelDB Authors. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form…
Finally, people are beginning to realize the insanity of this entire PATENTS file situation! When I first brought up how misguided people were for embracing React and projects with this license, I was downvoted to hell on HN. But really, everyone, THINK ABOUT IT. This is a company that glorifies and celebrates IP theft from others, and lionizes their employees who successfully clone others’ projects. They’ve built th…
I was interested in React based on what I'd read and was figuring it'd be worth looking into, but this provides all the reason I need to avoid it - I don't forsee a situation where I would personally or as a small company be suing Facebook, but I could see developing something then selling/trying to sell it to a larger company. If my code comes with a big side of "oh, and if you buy this you won't be able to sue Face…
You can't avoid react because it started a new paradigm. 9 out of 10 frameworks are based on the same principles and native follows suit where even big vendors are changing their strategies for mobile and desktop to align them with reacts principles (react-native, microsofts react-native-windows, reactxp and office fiber, googles kotlin for android, litho, componentkit, etc). Switching from react to something else is…
Earlier quoted context omitted.
This is not a copyright assignment and not an authorization to publish under a different license. Canonical's CLA adds the additional paragraph to enable that: Based on the grant of rights in Sections 2.1 and 2.2, if We include Your Contribution in a Material, We may license the Contribution under any license, including copyleft, permissive, commercial, or proprietary licenses. As a condition on the exercise of this…
True, it's not a copyright assignment, so Facebook should probably maintain the list of copyright owners somewhere (e.g. Go has (C) Go Authors and the list of authors is in a separate file), however, the CLA terms I quoted allow sublicensing. When signing the CLA, you grant Facebook the copyright license to your contributions, which Facebook then sublicenses to everyone else with the license of their choosing (as lon…
Earlier quoted context omitted.
It's called PR and google has mastered that art. I dare them to open source gmail's spam filter. There are so few email solutions right now out there. They are basically a monopoly. They could use some competition. Feel free to downvote google fanboys :). You're no different from MS fans for 90s
Open sourcing the spam filter will only help spammers. It is unlikely that it would work on an individual server with small amount of traffic. Instead of trying to make a perfect spam filter we should abandon outdated inreliable mail transfer protocol.
Earlier quoted context omitted.
Honestly, I didn't read the fine print. I've been having fun playing around with it. I assumed the license was OK considering its popularity.
"I assumed the license was OK considering its popularity." Always check the licence. Public domain, MIT, simple, plain BSD, GPL (any version), apache - if it's anything else, be extremely cautious.
Finally, people are beginning to realize the insanity of this entire PATENTS file situation! When I first brought up how misguided people were for embracing React and projects with this license, I was downvoted to hell on HN. But really, everyone, THINK ABOUT IT. This is a company that glorifies and celebrates IP theft from others, and lionizes their employees who successfully clone others’ projects. They’ve built th…
Earlier quoted context omitted.
You are in a better place though - because you're not the only react user. If indeed it turns out there are some submarine react patents facebook owns, with this patent license most other users can continue to work. Without the license, facebook then has the choice to either sue everybody (kind of unlikely) or to create the situation wherein suddenly everyone knows that they're infringing but haven't yet been sued, o…
> no large company is every going to agree to such an assymetrical deal. The thing is, if you just use react for something inconsequential, and can live with the fact that you have to cease using it when you sue Facebook, then it is fine. You shouldn't base your business on Facebook's (potential) patents, and then attack them with your own patents - but that is true with or without the patent grant. Of course, what w…
The chilling future effect, which I believe is the primary driver of op worries, is what if you build on React and are the next Facebook? (I.e. you are growing quickly to become "big enough" but are not yet)
Old Facebook now how a lot more leverage on you at several critical moments -- either in terms of making an offer, or in the negotiations around a more reciprocal patent licensing deal, or the aforementioned infringing of your patents, or the mere threat of either if someone else makes an offer.
The entire point of ladder kicking is to build a moat to ensure that others can't grow past you in the same way you did, and this is pretty effective at that (intentionally or unintentionally).
As you said, a more reciprocal, more finely-scoped patent balance would resolve these concerns. (E.g. "if you sue Facebook over a patent involved in React...")
Earlier quoted context omitted.
"I assumed the license was OK considering its popularity." I would have too. I'm getting into Clojure(Script) where React(Native) seems to be a popular choice for UI. I haven't touched it yet. I hope there's a good alternative when I get around to it because I really like Clojure but I never wanted to rely on anything made by Facebook.
There is Reacl. https://github.com/active-group/reacl