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

391–400 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#391

Post by hypothesis »

yellowbanana wrote: post #255
gosukiwi wrote: post #91

Ugh, now not only you don't own your code ( ahem copilot cough ) you also don't own the tools to develop code. The direction the web is taking is worrisome. The issue is not so much senior devs, but new devs. If they start off with things like that, there' so much magic under the hood, they won't understand how anything works. They don't understand they don't own shit until it's too late. I remember when I first saw…

It's amazing how github is not open source, the biggest host of open source software is closed source?

And it might be fine as long as underlying building blocks are open sourced (git, etc).

There are open-source alternative(s) that support import of most things from github.

Re: GitHub’s engineering team has moved to Codespaces

#392

Post by linux2647 »

notdang wrote: post #327
linux2647 wrote: post #237

Earlier quoted context omitted.

No, the article pointed out that vim and Emacs users can ssh into the hosts and edit code there. No VS Code use required

There are lot more IDEs other than VsCode, vim and Emacs

No doubt. I use JetBrains' suite of tools and I wonder how this squares up with Codespaces

Re: GitHub’s engineering team has moved to Codespaces

#393

Post by jackling »

gnull wrote: post #294
jackling wrote: post #159

Earlier quoted context omitted.

What skills would developers really lose? Speeding up boarding seems like a win, not many skills are developed imo trying to set up you personal dev environment. It's mostly just frustrating when a company's tools don't work well on your machine.

Being able to manage the frustration could be one such skill. And also being ready to fix things instead of assuming that employer must set up a perfectly working environment for you. I bet smaller/poorer companies may want programmers who are ready to fix tooling when it (inevitably) breaks

I see your point, but I think increasing productivity may be worth potentially losing some of the skills you mentioned.

Additionally, it's not like developer set up is the only thing that test your ability to manage frustration. I would say developer set-up is just something you need to get through to start your actual job, and if that can be eased up then it's worth it imo.

For smaller/poorer companies, they could always hire an engineer that specializes in fixing broken tooling. Ultimately it's a company's job to hire competent engineers.

Thinking back to all the times I had to set up my workspace, I wonder how much did I really learn vs just Googling and getting quick fixes.

Re: GitHub’s engineering team has moved to Codespaces

#394

Post by [deleted] »

wolverine876 wrote: post #353
hackthememes wrote: post #31

So you're telling me that the next GitHub outage could take out my dev environment and give me an afternoon off? Time to convince management that we need to switch to Codespaces!

There are different risks, but there is not necessarily more risk. Does Codespaces have lower or higher than the availability risks of your current environment?

[deleted]

Re: GitHub’s engineering team has moved to Codespaces

#395

Post by anthony_r »

greyhair wrote: post #388
anthony_r wrote: post #383

Earlier quoted context omitted.

Lol, like Microsoft paid the billions to give it out now for free. Besides, do you want your index funds to do well? Because that's exactly where the proceeds go to.

More than that, github was floundering economically, and Microsoft bought them to ensure continuity, because Microsoft was the single largest user. Don't want to rely on Microsoft for GitHub? The underlying 'git' is open source. Just deal with your git repos raw. No one is forcing you to use github.

> More than that, github was floundering economically

I do not think we actually know that. Was there any release of any financial data?

Also, part of the "beauty" of the modern "tech" giants is that they manage to find alternative sources of revenue, in some cases (notably Google and Facebook) completely replacing the old school user subscription revenue. By and large people seem to be OK selling their data for either a price reduction or complete price removal for services. It is what it is.

Re: GitHub’s engineering team has moved to Codespaces

#396

Post by nsonha »

BiteCode_dev wrote: post #310
zamalek wrote: post #207

Earlier quoted context omitted.

I've been playing around with a homegrown version of this. It's really not that hard: just set up a docker context to your home lab server and use VSCode remote containers. I've been able to remove WSL from my PC: Docker desktop was gouging itself on resources. I can now also shut down my desktop and continue exactly where I was on my laptop, and visa-versa. I don't have to pull WIP commits back and forth between the…

So how do you edit media files, using some ssh fuse mount magic ? What happen when you need to work from a shitty internet network ? In train ?

You edit media file in an editor?, wouldn't you just upload it? You can drag& drop into vscode and probably find the path to the tmp folder and work off that too.

Re: GitHub’s engineering team has moved to Codespaces

#397

Post by zamalek »

BiteCode_dev wrote: post #310
zamalek wrote: post #207

Earlier quoted context omitted.

I've been playing around with a homegrown version of this. It's really not that hard: just set up a docker context to your home lab server and use VSCode remote containers. I've been able to remove WSL from my PC: Docker desktop was gouging itself on resources. I can now also shut down my desktop and continue exactly where I was on my laptop, and visa-versa. I don't have to pull WIP commits back and forth between the…

So how do you edit media files, using some ssh fuse mount magic ? What happen when you need to work from a shitty internet network ? In train ?

> So how do you edit media file

This only does code. You'd probably have to do those locally and SCP them over or, yeah, some mount magic.

> What happen when you need to work from a shitty internet network ? In train ?

You'd have to commit your work, but you'd be able to bring the environment up on your laptop. There are still merits to this, such as the repeatable nature of containers. Depending on where you've worked, you may have been through the hell of a huge list of setup steps when on-boarding a project: that's one thing that containers are really good at automating.

You may not be the target audience, though.

Re: GitHub’s engineering team has moved to Codespaces

#398

Post by nsonha »

selykg wrote: post #229
swiley wrote: post #125

Earlier quoted context omitted.

I think people like not having their physical machine tied to their dev environment. IMO "the way" to do this is with ssh and tmux, not a web app. As long as people have choices I guess it doesn't matter.

If you read the article, that's an option with Github's code spaces setup. > Visual Studio Code is great. It’s the primary tool GitHub.com engineers use to interface with codespaces. But asking our Vim and Emacs users to commit to a graphical editor is less great. If Codespaces was our future, we had to bring everyone along. snip > From there, GitHub engineers can run Vim, Emacs, or even ed if they so desire.

The lame part is that they have to spin up vscode just to ssh

Re: GitHub’s engineering team has moved to Codespaces

#399

Post by jacobr1 »

minimaxir wrote: post #142
Raed667 wrote: post #135

Earlier quoted context omitted.

The difference is that you don't pay a monthly subscription to use a garbage collector.

Garbage-collection-as-a-service would get a ton of venture capital though.

There are a ton of a companies that help you track cloud spend, while some of it is architectural, most is really about waste, old ec2 image backups, s3 with no lifecycle policies ... garbage

Re: GitHub’s engineering team has moved to Codespaces

#400

Post by rightbyte »

Boxxed wrote: post #241

I feel like all of the problems in the blogpost are solvable without moving everyone to this crazy web development environment. To quote one of the proponents: > I do solemnly swear that never again will my CPU have to compile ruby from source. ...yeah, why was that even happening? Why not distribute pre-built artifacts? I feel like the whole docker ecosystem only exists because people forgot how to distribute softwa…

Fighting configuration complexity with another abstraction layer ... enabling the devs to pivot to pushing even more brittle code then ever before.
Post reply on HN