GitHub Codespaces

Re:GitHub Codespaces by sneak on Wednesday May 06, 2020 @01:01PM (#23093448)

There are perpetual reminders all around that Microsoft's only pretending to like f/oss because that's where the developer attention (and thus corporate money) is. There's spyware in all of their open source apps (TypeScript excluded, because they couldn't get away with it there) that you can of course patch out, but you can't get it removed from the project because, free software or not, Microsoft gets to decide what goes in or out.

Bet you a dollar the GitHub mobile app that's going to come out pretty soon will also be totally proprietary with no source provided. It's a growing trend in developer tooling: even Docker's desktop versions (not Microsoft's fault, but still) are not even open source (much less free software).

It's going to be really sad in a few years when Microsoft starts turning the screws to extract more revenue from this free software ecosystem (GitHub/npm) that they are coming to exert major control over.

Soon, the most common "industry standard" tooling for the largest and most popular software development ecosystem (javascript) will rely heavily on proprietary software that spies on you continuously while you use it, just like Windows.

[ Parent | on HN ]

Re:GitHub Codespaces by oefrha on Wednesday May 06, 2020 @01:07PM (#23093524)

> Bet you a dollar the GitHub mobile app that's going to come out pretty soon will also be totally proprietary with no source provided.

Stable version already came out a while ago, been using it on my phone. Also, GitHub the website has never been open source and they never pretended it was or was going to be, so no one was holding breath for source code of the mobile app.

[ Parent | on HN ]

Re:GitHub Codespaces by saagarjha on Wednesday May 06, 2020 @01:13PM (#23093617)

I mean, they could have totally released the source and it probably wouldn’t impact their bottom line at all.

[ Parent | on HN ]

Re:GitHub Codespaces by jon-wood on Wednesday May 06, 2020 @01:57PM (#23094216)

It would make quite a dent in support contracts for their on-prem offering.

[ Parent | on HN ]

Re:GitHub Codespaces by snazz on Wednesday May 06, 2020 @02:29PM (#23094594)

I'm pretty sure it wouldn't. The mobile app isn't something that requires a ton of support anyway. What good would the source code do you in this case?

[ Parent | on HN ]

Re:GitHub Codespaces by jannes on Wednesday May 06, 2020 @03:16PM (#23095122)

I think jon-wood was talking about the website’s source code, not the mobile app.

[ Parent | on HN ]

Re:GitHub Codespaces by meysholdt on Wednesday May 06, 2020 @01:45PM (#23094041)

The view of the Eclipse Foundation onto VS Code may be interesting here: https://blogs.eclipse.org/post/mike-milinkovich/theia-open-s...

[ Parent | on HN ]

Re:GitHub Codespaces by knodi123 on Wednesday May 06, 2020 @05:51PM (#23096741)

whoa, slick.

[ Parent | on HN ]

Re:GitHub Codespaces by carapace on Wednesday May 06, 2020 @01:24PM (#23093753)

Yeah, this.

The analogy seems clear to me: The web is to IE as git is to VSCode, eh?

At the very least, it makes it harder for an editor to be a competitor to VSCode w/o integrating with GitHub (not just git) now, eh?

[ Parent | on HN ]

Re:GitHub Codespaces by mr_toad on Wednesday May 06, 2020 @07:00PM (#23097435)

It’s telling that they went with VScode and not Atom. Makes me wonder what the long term outlook for Atom is.

[ Parent | on HN ]

Re:GitHub Codespaces by cema on Wednesday May 06, 2020 @05:04PM (#23096273)

Not really. At least: the web happened well before IE was introduced as an answer. In contrast, VS Code was invented much later than git which at the time was an established technology and in some ways a standard.

[ Parent | on HN ]

Re:GitHub Codespaces by zerkten on Wednesday May 06, 2020 @06:08PM (#23096916)

The other context here is that IE was a competitive browser in its time: 1998-2001. The problem is that it won and then languished. IE had a lot of sway over how developers built things as the market share grew. Then it locked in users in various ways which starved the other competitors.

It took until Phoenix (now Firefox), for there to be something better that grabbed the attention of developers and those sick of being stuck with IE. It became Firefox and Mozilla hatched a pretty effective plan to steal market share. For all of Mozilla's recent failings, we forget (or weren't around to remember) the success of Firefox was pretty impressive as it was a grassroots effort.

[ Parent | on HN ]

Re:GitHub Codespaces by kick on Wednesday May 06, 2020 @01:12PM (#23093599)

GitHub has always been a proprietary company unconcerned with user freedom.

They actually have a whitepaper that predates acquisition on exactly this:

https://resources.github.com/whitepapers/introduction-to-inn...

The company has always been unethical; Microsoft didn't change that.

[ Parent | on HN ]

Re:GitHub Codespaces by PanosJee on Wednesday May 06, 2020 @04:19PM (#23095794)

Wait for radicle.xyz

[ Parent | on HN ]

Re:GitHub Codespaces by yarrel on Wednesday May 06, 2020 @04:55PM (#23096177)

Those of you downvoting this - can you explain what you disagree with here?

Because it looks like a good analysis of this part of Microsoft's strategy to turn "Open Source" into a spyware-laden sausage machine for Azure.

[ Parent | on HN ]

Re:GitHub Codespaces by hamandcheese on Wednesday May 06, 2020 @05:11PM (#23096347)

I think the downvotes are because Microsoft has been providing some amazing tools completely free of charge. If that helps them sell more Azure... great! Everyone wins, except GitLab and AWS.

Calling it spyware is hyperbolic.

Keep it up Microsoft.

[ Parent | on HN ]

Re:GitHub Codespaces by cutler on Wednesday May 06, 2020 @07:38PM (#23097795)

Some of us have longer memories of Microsoft's game-plan - embrace and extend. With so man now willing to grant Microsoft open source cred don't forget that it wasn't so long ago that Microsoft was running a Linux patent racket. If we allow The Beast to monopolise open source development tools we have only ourselves to blame.

[ Parent | on HN ]

Re:GitHub Codespaces by eeZah7Ux on Wednesday May 06, 2020 @06:52PM (#23097357)

Microsoft has been adopting standards to then extend them and lock-in users for two decades.

> Microsoft has been providing some amazing tools completely free of charge

Yes, and they are the opposite of a no-profit.

This are just the first steps: "embrace" and "extend".

[ Parent | on HN ]

Re:GitHub Codespaces by sneak on Wednesday May 06, 2020 @06:40PM (#23097245)

Not at all. There are no objective criteria to define spyware that do not also apply to Windows or VS Code (and probably the GitHub mobile app, but I have not yet confirmed that).

[ Parent | on HN ]