And that made me curious. To be honest, I don’t really read the
npm installing package x. So when MDG announced that they were dropping Blaze (indeed; old news, they don’t seem to be doing this anymore), I started to research React purely on the tech, and I started to like it. So… I started to use it in our projects.
But now; triggered by the what @msavin wrote, (see the quote above) I researched a little on this subject. And it’s basically all about the PATENTS file that comes with each open source repo. This proves again,
open source is not per se free. In this case you seem to sell your company to Facebook by using its software. Or should I say you’re giving Facebook an option to buy claim your company on a later time; as that seems to be more correct.
Someone explained the issue perfectly well on Hacker News:
He writes about React Native, but this is also the case for React and even Immutable.js.
To be clear. This is not an issue for the individual developer that works on his hobby projects. But if you are running a reasonably sized company, this is most definite something to think about.
So at everyone that’s making money with the development of software; are you still using Facebooks libraries? How do you deal with this?
I thought this was a duplicate of this other related topic. But it’s not really. I’m interested here in a conversation about how to deal with licensing issues. Not about alternatives for the software: