Microsoft Github isn’t about social coding anymore: it is all for social conditioning now.
Yesterday Microsoft made another clear-cut action of posturing and virtue-signaling (much like their decision of not to sell certain technology to police departments). This time around they declared war on English language and made it clear to everybody that they are in a position to decide the meaning of the words for the rest of us. In particular, for the software development communities. Yes, I am talking about the contraversial and illogical step to remove common term “master” from their popular version control system Github.
Today, after almost ten years of being a customer, I have deleted my Github account and completely moved elsewhere. If you’re thinking about doing the same you can find ample alternatives from bitbucket.org to jetbrains.space with many options in between.
Replacing words in programming languages or changing their meaning has nothing to with social justice or better world. It is how big tech companies are flexing their muscles and exercise their control over software development crowd.
Submission or outright genocide through commercial meanings is what Microsoft was doing to Free Software and later Open-Source Software for years. This is what Microsoft keeps doing no matter how many times their management will say “we embraced open-source” or “we admit our mistakes in the past” – they still have the same agenda and they still do everything they can to submit open-source development to their command. Massive contributions into Linux Foundation and Apache Software Foundation are just that: a tactical moves to setup people who would be doing their bidding for them.
Perhaps open-source developers and other software professionals would hear this and hit Microsoft back exactly where it hurts: their P&L, user base and influence they should no longer have.
Hey LinkedIn – you’re next!
As you have seen in my last post or elsewhere, Facebook has recently added a dubious patent clause in the license of multiple projects including ReactJS. And predictably, a number of organizations, companies, and open-source advocates made it clear that it’s way too dangerous to keep on using the code with such restrictions because of possible legal repercussions.
Well, I am pleased to tell to all my readers, that they have back-tracked on this after Apache Foundation, WordPress, and many others have express their clear intention of switching to safe alternatives to React.js and other frameworks from FB, or banning their use. As you all know, FOSS is a free market ecosystem; it is thriving from the forces of intellectual competition, always offering multiple choices to its users. And this approach won again: facing the danger of loosing their user base and, effectively, rendering themselves irrelevant, they made the decision to, once again, re-license some of their projects under MIT.
Namely, ReactJS will be released under the new license. So if you are using it – make sure to update your dependencies to v.16 once it is out next week. Remember, re-licensing isn’t usually retroactive, so don’t fall into that trap.
Disclaimer: I am not using, planning nor recommending to use any Facebook’s sponsored projects
And let the Dao be with you, as usual 😉
In somewhat recent revelation about the pitfalls of infamous Facebook “BSD + Patents” license, FOSS developers becoming more acutely aware and alarmed about the consequences.
I won’t bother you with much details, as they are readily available elsewhere. I just want to point out that Facebook is hedging their open-source “exposure”. What they are effectively saying is “Go ahead and use our awesome stuff. But if we ever decide that you’re competing with us, we’ll yank your licence to use our frameworks so fast your shoes will fall off.” It doesn’t matter if someone has developed this code for you: you won’t be able to use it anyway.
That’s the essence. It is the original intention of the license behind ReactJS and a few other frameworks. And that’s why Apache Foundation has moved the license to Cat-X, prohibiting any of its projects to touch things like ReactJS. Facebook software is NOT compatible with the projects developed under widely accepted and respected ALv2.
Here’s the excerpt:
Facebook BSD+Patents license
The Facebook BSD+Patents license includes a specification of a PATENTS file that passes along risk to downstream consumers of our software imbalanced in favor of the licensor, not the licensee, thereby violating our Apache legal policy of being a universal donor. The terms of Facebook BSD+Patents license are not a subset of those found in the ALv2, and they cannot be sublicensed as Alv2.
These are the unintended consequences of meddling with well thought open-source software licenses. That is the beauty of open-source: if you trying to lock people in or out – they will move. It doesn’t matter how much money you have, how big you are, nor what your SJW position is. Developers will go, and the users will as well.
I’m sure we haven’t heard the last of it yet. And that’s the damning and loud application of the golden rule!
The first thing you see entering to the Strata 2013 exhibition is hugely tasteless Miscrosoft booth that is sitting in the premium spot of the floor right next to the front doors. Later update: don’t believe me: check this
//platform.twitter.com/widgets.js This year BigData conference was largely focused on Hadoop and downstream technologies: HBase, Spark, and so on. As most of you would know, this technological niche is based on two open source whales: Java/JVM, and Linux. Now, unless you spent last 15 years on Mars, you would know that there’s no love lost between the Microsoft and open source community. And don’t hurry to blame open source for this endless assault. Check just a few results from Google search in vague chronological order ranging from 1998 to 2012:
And there are many other evidences that you can easily dig up by just scrolling through about 56,000,000 articles found by Google.
Some apologists might say “The Microsoft has changed lately”. Really? Banning Linux from booting on ARM based Windows 8 devices is just an honest mistake then, I presume.
Perhaps “It is their hardware and they can do whatever they are pleased” other pin-heads might say. Do I need to answer this? How about me paying for the hardware? Do I own it now? Or am I just leasing it from dudes up in Redmond, WA? Do I need to go down to basic economical explanations about natural law?
And after all these heinous things they are coming to the midst of the open source celebration like nothing happens. They even sponsored the lunch on the last day of the conference. I think people who ate that poisoned stuff might find themselves enslaved to Microsoft via some kinda of EULA or something.
But joking aside, do these guys have a nerve or what? May be MS thinks they now are a king of the hill just by virtue of hiring for legwork this certain startup, who’s founders did a lot of the Hadoop initial work? Judge for yourself.