Skip to main content

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"... people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own features so will the ones who oppose this purchase do the same? Will they become the trolls?

I've often expressed concern about how Microsoft builds up and then quietly gets rid of technology. I appreciate their right to do so but for corporate developers, it's frustrating. It has pushed many developers to leave the shadow of the "evil empire" for greener pastures. however, the hatred some developers have for Microsoft flies in the face of common sense.

Open source software suffers from the same potential stagnation or loss of support that commercial software does. In many ways it's worse - the current state as well as future of an open source technology depends on how many people flock to it and people, yes, even developers, can be fickle. At least in commercial software, it can rely on a company's belief in its benefits or emotional attachment to it.

GitHub's lack of financial stability was a very big risk, especially as they encourage companies to store their commercial source there.  Now that stability can be assured, in as much as it is possible.

Microsoft has made a lot of progress from its days as a "lock everything down, we don't share" company. Some of those strides were mandated but in other cases, it was pure competitiveness. But where is OpenOffice today? It released its latest version last year but has lost a lot of its earlier momentum. Instead the focus has been on open source formats, something that Microsoft has fully supported. Microsoft has listened to many of its employees as well, releasing technologies into the open source community. But this has done little to quell its detractors.

If Google had bought GitHub, developers would rejoice but everyone would have been forced to have a Google account. If FaceBook had bought it, the loss of teens to the community might have been reversed. If Apple had bought GitHub, it would have made Tim Cook appear on more than just one network and have a huge public media splash --- oh, that would have made WWDC a bigger draw. But Microsoft? Hell no.

Now is their opportunity to provide an alternative to GitHub, if, of course, they can maintain it. Or they can move back to SourceForge (although this might be akin to going to MySpace after FaceBook).

Regardless of how evil one can be, everyone loves to believe in redemption, except, it seems, in Microsoft's case.



Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...