Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub’s engineering team has moved to Codespaces

github.blog

Post reply on HN
Print view View original

561–570 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#561

Post by jorams »

Barrin92 wrote: post #481
leppr wrote: post #443

Earlier quoted context omitted.

The MS that's killing their own single most popular product, Windows, with anti-user features, is the MS of now . Releasing VS code and WSL doesn't redeem their sins.

is this not another example of the 'HN echo chamber'? Is Windows market share budging? Windows currently is by far not the worst iteration of the OS and nobody gives a crap about anti-user features which everyone has had to deal with for literally decades

> nobody gives a crap about anti-user features which everyone has had to deal with for literally decades

The one thing that used to set Microsoft apart from the likes of Google and Facebook was that their main product, Windows, was not anti-user. No matter what you thought about the OS or Microsoft's business practices, it was a paid piece of software that worked for the user. Windows now is filled with user-hostile features and it works for MS instead. And they don't even grant us the courtesy of giving it away for free.

Market share or the fact that the public at large isn't punishing them for it doesn't mean anything. It was already clear that most people are willing to walk headfirst into a dystopia.

Re: GitHub’s engineering team has moved to Codespaces

#562

Post by jabo »

atsaloli wrote: post #487
tgsovlerkhgsel wrote: post #482

Earlier quoted context omitted.

I really hope that if this happens, DPAs bring the hammer down on everyone involved (both MS and companies using it) in a useful timeframe (i.e. before it has become socially acceptable because "everyone is doing it" and there are no consequences).

What’s a DPA, please?

Data Processing Agreement: https://gdpr.eu/data-processing-agreement/

Re: GitHub’s engineering team has moved to Codespaces

#563

Post by Aeolun »

015a wrote: post #190
tiffanyh wrote: post #90

> "So we moved to 32 core, 64 GB RAM VMs. By changing a single line of configuration, we upgraded every engineer’s machine." On GitHub, that instance type is $2.88/hour or $2,073 monthly per developer for a single instance. (Granted, that's running 24/7 but still - wow, that's expensive for a single instance)

That pricing is a ~70% markup over standard Azure rates. Companies typically buy laptops with an assumed 3 year lifespan; so, let's assume a high-end $3000 laptop, that would be ~$83/month. Of course, you need a computer to access Github Codespaces, so this isn't saving all of that money. Maybe companies can cut some costs by buying cheaper laptops? Or if you want a more apples-to-apples; a Lenovo ThinkStation P620 r…

I don’t think they’re trying to save on hardware costs here. This is to prevent any kind of friction and wasted time when switching between branches/environment.

If your dev costs you $100/h, you only have to save them +/- 5 hours of faffing around with branches/dependencies every month to make it worth it (assuming a 8 hour workday).

Re: GitHub’s engineering team has moved to Codespaces

#564

Post by gscho »

lucideer wrote: post #22

> My friends, I’m here to tell you I was a Codespaces skeptic before this started and now I am not. This is the way. ~@iolsen I don't actually doubt that this (and the 4 other glowing employee quotes) are real, but even assuming they are, I can understand people remaining skeptical about the sample size of 5 being broadly representative of the 100s (1000s?) of engineers at the company. Also slightly hilarious that "T…

Thank you for ruining the mandalorian. I just started season 2.

Re: GitHub’s engineering team has moved to Codespaces

#565

Post by Aeolun »

metaltyphoon wrote: post #296
z77dj3kl wrote: post #245

Earlier quoted context omitted.

It's a slightly different flavor of the same thing. VS Code is an amazing tool that's getting huge adoption because of how awesome it is, and how open source and community centric it is, etc. They've gotten a lot of mindshare and dev love, that's the embrace bit. The next step is the set of closed source addons. Have you noticed that a lot of the new VS Code features are now in addons that are under a different licen…

Gotta love how the goal post just keeps moving forward.

More like you never know when they’ll initate the final part of their strategy.

Half the dev world is now used to VS code. Many junior developers have never used anything else. Whatever they do can have a big impact.

Re: GitHub’s engineering team has moved to Codespaces

#566

Post by MisterSandman »

015a wrote: post #190
tiffanyh wrote: post #90

> "So we moved to 32 core, 64 GB RAM VMs. By changing a single line of configuration, we upgraded every engineer’s machine." On GitHub, that instance type is $2.88/hour or $2,073 monthly per developer for a single instance. (Granted, that's running 24/7 but still - wow, that's expensive for a single instance)

That pricing is a ~70% markup over standard Azure rates. Companies typically buy laptops with an assumed 3 year lifespan; so, let's assume a high-end $3000 laptop, that would be ~$83/month. Of course, you need a computer to access Github Codespaces, so this isn't saving all of that money. Maybe companies can cut some costs by buying cheaper laptops? Or if you want a more apples-to-apples; a Lenovo ThinkStation P620 r…

It's not worth it right now. The economies of scale could add up to make it break even, if not be cheaper.

Big could, of course. But considering it takes new devs at my company ~3 business days to get up and running (and we're a React shop), it could be worthwhile.

Re: GitHub’s engineering team has moved to Codespaces

#567

Post by jrochkind1 »

genewitch wrote: post #509
jrochkind1 wrote: post #490

Earlier quoted context omitted.

oh right, my home lab server, that must be around here somewhere...

I have an HP 4u from 2010 with 80 threads and I think a quarter TB of memory, 6 SAS, and 2 1TB ssd, currently running Ubuntu 16 and Wok, for VMs. It took a lot of effort to get this working and it's still a huge pain - I have no UPS for it since it uses 220VAC, and UPS cost more than the server cost me, for example. I can't use docker in general because my internet is too crappy. That was annoying in 2012 when I firs…

> It took a lot of effort to get this working and it's still a huge pain

You make an attractive case it for! :) Yeah, this is why I don't have a "home lab".

Re: GitHub’s engineering team has moved to Codespaces

#568

Post by harryvederci »

whichquestion wrote: post #473
blacktriangle wrote: post #455

Earlier quoted context omitted.

That's the trick, the git is open, but the metadata is what matters. Issues, PRs, integrations into various code auditing services. That's the whole "extend" bit.

Are there any foss initiatives to making these metadata bits portable?

https://fossil-scm.org/

Re: GitHub’s engineering team has moved to Codespaces

#569

Post by endgame »

Buttons840 wrote: post #551
kjksf wrote: post #385

Earlier quoted context omitted.

If they do, the competition is just a click away: https://www.gitpod.io/

How about moving all our code off GitHub while we're at it? In this worst case scenario (which hasn't happened yet), I'm sure GitHub would expect the good will of open source projects and contributors while simultaneously being the boot on their face in the workplace.

I've been on sourcehut for a while now. It's great.

Re: GitHub’s engineering team has moved to Codespaces

#570

Post by brundolf »

dchuk wrote: post #543
brundolf wrote: post #272

Earlier quoted context omitted.

I recently set up a home Linux server and I've been doing my personal projects on it via VSCode's remote development (from my MacBook and my Windows desktop). The server isn't actually as powerful as those machines, but the convenience of having a single env regardless of client has still been fantastic (not to mention getting all the Linux niceties despite working from Windows). Doing it in the cloud probably carrie…

How are you accessing the box away from your local network? Just exposing the box to the internet via your router or using something like Tailscale?

Tbh I haven't gotten that far. Of course, I also haven't really had the need yet with covid times
Post reply on HN