Live data from Hacker News

GitHub’s engineering team has moved to Codespaces

github.blog

51–60 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#51

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!

It's funny timing to announce this the day after a major outage that took down practically the entire platform

Re: GitHub’s engineering team has moved to Codespaces

#52
post #47

I would quit so fast if my company forced me to use a web IDE.

GitHub isn't forcing anybody to use a web IDE. The most broadly used access interface is VSCode. Then there are heretics like me who choose to ssh in so we can use Vim. This is described in the article.

How does setting up a desktop IDE work?

Re: GitHub’s engineering team has moved to Codespaces

#53

I would quit so fast if my company forced me to use a web IDE.

I would be happy to let go of an employee who bank their employment on the preference of toolings.

Hear me out:

Toolings are, like the name suggests, a means to an end. If a web IDE is fast, works reasonably, and can continue improve itself. And the learning curve is friendly to engineers with different background and experience. Everyone should be comfortable to be nudged to use it. And if the tool additionally is a critical product of the organization, everyone should be comfortable to be mandated to use it, because it's now a very valuable source of dogfooding.

Re: GitHub’s engineering team has moved to Codespaces

#56

Earlier quoted context omitted.

I'm in the GitHub Codespaces personal beta: counterintuitively, the UI/UX of Codespaces is as performant as VS Code on the desktop.

I also don't use VS Code usually. My personal preference is a JetBrains IDE, but my point is more engineers should be able to choose the environment they're most productive in.

Currently, VS Code is the primary method of connection to each Codespace, and we do not support other editors officially.

If you’re looking to connect via SSH, we do have a workaround here: https://github.com/microsoft/vscode-dev-containers/blob/main... -- and I use this regularly for Jupyter Notebooks.

Re: GitHub’s engineering team has moved to Codespaces

#57

Earlier quoted context omitted.

Note that they mainly use VS Code and also support vim and emacs.

Like, Vim and Emacs keybindings? Or real Vim and Emacs? It's quite different xD

They let you ssh in. So you can run vim/emacs on the machine if you want.

Re: GitHub’s engineering team has moved to Codespaces

#59
post #5

locked-in to visual studio code? no thanks

The article mentions supporting vim and emac, which probably means any editor can be supported. 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. Happily, we could support our shell-based colleagues through a simple upda…

> support our shell-based colleagues

What do vim and emacs have to do with the shell?

This is another case of people thinking "shell" is synonymous with "TUI", which is false.

Re: GitHub’s engineering team has moved to Codespaces

#60
post #8

Earlier quoted context omitted.

I write all my code on my personal laptop and then retype it into my company's IDE

That seems unnecessarily complex and time-consuming. Unless your company's work machine is locked down and you can't be productive on it...

If the company IDE is annoying to use, then rewriting it is probably a net time saver. The time consuming part of coding is rarely typing the code, afterall.
Post reply on HN