6 ms·
Haven't used it. Was considering it till I read the license rubbish. I use ionic and I'm quite happy with it. It's not Native, but for 80% of the apps out t
by segmondy 9y ago
Haven't used it. Was considering it till I read the license rubbish. I use ionic and I'm quite happy with it. It's not Native, but for 80% of the apps out there it's create and there are lots of native Cordova plugins and you can write your own if you need missing native capabilities.
- publicfig 9y agoI'd recommend reading this article about the licensing language that's being disputed now: https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revokable-patent-license-why-its-a-paper-25c40c50b562 https://medium.com/@dwalsh.sdlr/react-facebook-and-the-revok... The author is the same person that has an article on the front page currently arguing that the license for Graph QL DOES have issues (and is following through with Facebook through Github Issues to resolve them), so I think this position is really worth considering.
- rjmunro 9y agoJust delete the PATENTS file. There is nothing that says you can't do that, and you then have a plain BSD licensed project.
- ballenf 9y agoThe downvotes suggest no one is taking this seriously, which is good. Because as soon as the first React patent issues such a project would be an immediate willful patent infringer. At least in the US or anywhere else software patents are recognized and have been filed.
- sandGorgon 9y agoSame here. We were seriously considering it, until the licensing issue. In fact, we continue to use Reactjs - because it is something that we can rip out and replace if push comes to shove. But a React Native app once released will live in the wild - which means the patent exposure cannot be mitigated easily.