←back to thread

Important open source projects should not use GitHub (2020)

(unixdigest.com)
68 points bitbasher | 1 comments | 15 Apr 25 02:18 UTC | HN request time: 0.207s | source
Show context
decide1000 ◴[15 Apr 25 11:32 UTC] No.43691342[source]▶
The reason I don't use Github is Microsoft's hatred stance on open source.

Anyone remember Microsoft calling Linux a "cancer"? Or Microsoft threatening open source developers for violating 200 patents? Or their official stand where they whould threaten and fear Linux devs? The secretly funded lawsuits against Linux? They even threatened lawsuits at companies for just using Linux.

This company is rotten by the executive level.

replies(1): >>43693907 #
FireBeyond ◴[15 Apr 25 15:09 UTC] No.43693907[source]▶
A lot of that was valid twenty years ago, and they certainly burned many bridges.

Now there's VSCode, TypeScript, WSL, Dapr and .NET, all open source.

replies(2): >>43694236 #>>43701802 #
bitbasher ◴[15 Apr 25 15:30 UTC] No.43694236[source]▶
VSCode itself was a malicious move by Microsoft to capitalize on Atom's success, followed by the acquisition of Github and the beheading of Atom.

VSCode is "open source" with a walled garden of a marketplace. A quick look at how Microsoft is trying to kill competitors like Cursor (within the last week) by squeezing them out of the walled garden is... telling.

These moves by Microsoft are not made in the spirit of open source. It's in the spirit of EEE.

replies(1): >>43713594 #
1. goku12 ◴[17 Apr 25 06:08 UTC] No.43713594[source]▶
Big corporations are not monoliths, despite them having an overall singular personality. I believe that vscode was a sincere attempt, at least in the beginning. While based on electron which was originally developed for Atom, vscode was always much more performant than atom.

But when it did gain a lot of developer attention, MS's true nature took hold and gradually converted it into the walled garden we see today. It was more subtle in the beginning - a few useful extensions were proprietary and wouldn't work on non-MS builds of vscode for some unspecified reason. It was like a gentle nudge to the developers to migrate to their opaque proprietary builds. Of course, we have seen that before, haven't we?

As an aside, if you like vscode but hate the manipulation, you should give the Eclipse Theia editor [1] a try. It's an almost complete reimplementation of vscode and is compatible with the extensions from OpenVSX. I believe that they have fairer alternatives for collaborative editing, etc. At least, they will spare you the manipulation.

[1] https://theia-ide.org/