This description of React's patent situation by an actual patent lawyer sums up my understanding nicely:https://blog.cloudboost.io/3-points-to-consider-before-migrating-away-from-react-because-of-facebooks-bsd-patent-license-b4a32562d268 …
-
-
That's your issue. And it *is* an issue. But (many) other devs just want to know how it affects *their* project. Today.
-
Devs at big companies should ask their lawyer. Devs at small companies or OSS should consider the community implications.
-
No categorical right/wrong good/bad here. Considerations vary for each co., dev, project. As any lawyer can tell you, "it depends..."
-
Yep. People have started citing you as legal advice "from an actual patent lawyer". Probably not your intent (or what you wanted)
-
Well, I am an actual patent lawyer (been called worse...
) but anyone citing my article as "legal advice" probably didn't read it:pic.twitter.com/H8upJRrGPK
-
"don't worry about it" is definitely advice when made citing your article. No?
-
Dunno. I think tone of the article is clear that it's raising issues ("3 Points to Consider...") not advising X or Y.
-
A few things: 1. It's definitely being cited as legal advice. 2. Your tweets have gone further.https://twitter.com/ArielR_IP/status/909483656477134849 …
- 4 more replies
New conversation -
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.