@jd The article's interpretation of EEE is incorrect. Embrace is about adopting free software protocols. Microsoft putting lots of stuff on github is still part of Embrace.
Extend is about adding "value add" to the protocols, beyond what the free software tools offer, available only using proprietary tools. This creates gravity toward the proprietary tools.
Extinguish is when compatibility with free software can be abandoned entirely, because most people are using the extended protocol.
Buying the biggest service in the space allows Microsoft to go down the Extend route. Github already has Extended git-adjacent space by providing issues and pull requests that cannot trivially be integrated with other hosts and free software tools. The reason github attracts projects is not because they're so good at hosting git repos. It's because of git's integration into their proprietary services.
Google font: they serve the font file to your visitors. It's a file transfert. So, they collect a log entry on their server with their IP/browser/where-they-came-from/etc... and because many dev use Google-font, they have a map of most of your visitors move accross the internet.
@Antanicus And, it may amuse you to learn that when I say these things (no patents, more design for permaculture and nutrition) to other science advocates, they often immediately assume I'm against GE and science generally. The effect cuts me both ways: everyone things I'm the other camp. Me, I hate camps.
Microsoft owns LinkedIn and Github, so they deliberately acquire spaces that synonymise themselves with aspects of the hiring process? Theyβre going all in on technological enterprise solutions which is smart honestly
@sophia Where I work our job application forms used to have a field that read "github profile", until I requested a change to "code repository hosting profile". It was never the case that we'd reject gitlab or a self-hosted repo, it was just a cultural default.
@azuresource This is not the first gitocalypse, there was also the gitoriocalypse when gitlab acquired gitorious. So githubocalypse may be more appropriate. I prefer to call it #MSFTGothub and let people add their own level of apocalyptic connotations.
Looks like gitlab has an auto import feature for moving from github, so I guess I'll be going with them for now. (You can find it by selecting projects, then selecting new project). #gitpocalypse#gitgeddon#embraceExtendExtinguish
There is no way that any code I wrote will fall under the dominion of Microsoft.
Therefore in the coming week I'll be moving out of Github. Initially I'll just self-host on Gogs, but I'll also be looking for a secondary host as backup for cases where my own server is down or doesn't have enough bandwidth.
I'm sure that this will be rough for a lot of projects. Many things currently point to Github. Some will side with Microsoft, believing that they are allies of FOSS or just favoring convenience over disruption. When Microsoft is involved this is always a mistake.
@ajeremias @Antanicus@alfred@ej Again: the IARC monograph was constructed using carefully selected studies to designate Glyphosate as a carcinogen. It excluded studies that found it safe. And they could still only make it look "as bad as coffee". The process by which they did this, has attracted a lot of scrutiny. The chairperson of the study group, it turns out, is an unqualified activist. Not a toxicologist. Toxicologists, meanwhile, agree.