4 ms·
The post is wrong about React changing the BSD+Patent license. It hasn't changed and is still an issue, depending on who you ask. [0] https://github.com/facebo
by thingerr 9y ago
The post is wrong about React changing the BSD+Patent license. It hasn't changed and is still an issue, depending on who you ask.
[0] https://github.com/facebook/react/issues/10191# https://github.com/facebook/react/issues/10191#
[1] https://code.facebook.com/posts/112130496157735/explaining-react-s-license/ https://code.facebook.com/posts/112130496157735/explaining-r...
- fortythirteen 9y agoThat second article is a total cover-up. By that PATENTS.md file, Facebook could totally ream a company by doing the following: 1. Identify a competitive service or one that FB would like to build into their offerings, that is currently using React. 2. Litigate against that company, with any patent claim, whether justifiable or not. It will take months, if not years, for even the most frivolous suit to get thrown out. 3. Use the litigation period to revoke the company's license to React, effectively shutting down their product.
- tuxracer 9y agoPreact https://preactjs.com/ https://preactjs.com/ is a good purely MIT licensed drop in replacement for React if licensing is an issue
- elliotec 9y agoIt claims to be a drop in replacement, but it isn't.
- garfij 9y agoCan you expand on this at all? I've looked at it as a replacement and I understand there are things like prop-types that are missing, but my understanding is that there are other libraries you can can use in addition to preact that give you 100% compatibility.