GitHub’s engineering team has moved to Codespaces • Hacker News Board

Re: GitHub’s engineering team has moved to Codespaces

#701

Post by prirun » Sat, Aug 14, 2021, 5:49 PM UTC

ChicagoDave wrote: post #690

prirun wrote: post #671

Earlier quoted context omitted.

Microsoft plays a very long game. 3-4 years is not enough time to boil a frog; it takes much longer or the frog will realize what's happening. Be patient. Give them 10-15 years after their "We love Linux" shift and you'll see. They love it so much, they will own it. Just think of Microsoft like the Borg.

Microsoft is a trillion dollar company in large part because they embraced open source. Azure is extraordinarily profitable. Why would they fuck with their number one audience, developers?

According to this site, Microsoft's profit is divided into thirds:

https://www.investopedia.com/how-microsoft-makes-money-47988...

A third is for Office, a third for cloud, and a third is Windows.

IMO Microsoft is a trillion-dollar company because of their long monopoly with Windows. It's so entrenched that their "punishment" for abusing their monopoly position (according to the DOJ) was to give all schools free copies of Microsoft Office, thereby forcing every parent to own a copy of Microsoft office to be able to read reports from their kids' schools. Ingenious!

You know why they would fuck with developers? Because developers have choices now, and Microsoft doesn't like it when anyone has a choice besides Microsoft. They are remedying that.

Re: GitHub’s engineering team has moved to Codespaces

#702

Post by gray_-_wolf » Tue, Aug 17, 2021, 9:52 PM UTC

dcreager wrote: post #556

gray_-_wolf wrote: post #505

Earlier quoted context omitted.

It's not just that. There is also the matter of laptop getting broken (we all have proper backups, right? right?), stolen, ... So I do see the appeal in thin client. My only issue is that the experience his closely tied to latency, so sometimes working over ssh is... irritating. Especially on mobile connection.

It’s all Docker images under the covers, so our devs also have the option of downloading and running that image locally instead of in a Codespaces VM. That was always possible before, of course, but Codespaces gave us the impetus to invest the effort in Dockerizing the dev environment more rigorously.

Oh, that is cool. Sounds like a nice mix actually. Local vim, browsers, known system. And container with mount-bind to actually compile and run stuff in.

Re: GitHub’s engineering team has moved to Codespaces

#703

Post by CRConrad » Thu, Aug 19, 2021, 9:54 PM UTC

maccard wrote: post #663

pdpi wrote: post #584

Earlier quoted context omitted.

I can’t think of a single person I’ve worked with in the last 10 years who understands the difference between vanilla git and GitHub. Nobody really understands why pull requests are named that way, or that it’s possible to have very different workflows to what GitHub offers. I don’t know that this is the result of a deliberate strategy by GitHub, but by any metric the extend step is a resounding success.

> I can’t think of a single person I’ve worked with in the last 10 years who understands the difference between vanilla git and GitHub. If not one developer in a decade can tell the difference between a source control hosting service and a tool they use, that's not really GitHub's problem. This is the same as my parents not konwing that "facebook" isn't the internet. > Nobody really understands why pull requests are…

> If not one developer in a decade can tell the difference between a source control hosting service and a tool they use, that's not really GitHub's problem. This is the same as my parents not konwing that "facebook" isn't the internet.

Nobody said it was GitHub's problem just like nobody said it's Facebook's problem in your example. They're both laughing their heads off all the way to the bank. It's everybody else's problem.

Re: GitHub’s engineering team has moved to Codespaces

#704

Post by CRConrad » Thu, Aug 19, 2021, 10:00 PM UTC

maccard wrote: post #660

amatecha wrote: post #553

Earlier quoted context omitted.

You know how they added Github CLI[0], right? There may be a time where you must use Github CLI instead of a "standard" git client to interact with Github projects. That would be the "extinguish" phase. Right now they have embraced and are extending (such as with Github CLI). [0] https://cli.github.com/

I made this comment elsewhere [0], but by this logic anyone who builds an ecosystem for an open source tool should be accused of the EEE strategy. > There may be a time where you must use Github CLI instead of a "standard" git client to interact with Github projects So we're accusing MS of a slippery slope based on a phrase from 25 years ago, which there is absolutely zero proof or indication of them pursuing in the…

> I made this comment elsewhere [0], but by this logic anyone who builds an ecosystem for an open source tool should be accused of the EEE strategy.

Yes, of course.

Why, did you somehow think otherwise?