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

61–70 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#61

Post by aaomidi »

systemvoltage wrote: post #29

Is it just me or VSCode is dauntingly complex? There are so many configuration options and I often get lost in it. I've been using Sublime Text for a decade and it has kept the scope creep to a minimum. I've also used JetBrains IDEs and while there is a massive amount of complexity, it is well organized I think. I just get anxiety from launching VSCode, may be it is because of not being familiar with it, I don't know…

The configuration is complex, but in reality you don't need to touch any of the configuration for most development workflows.

The configuration also syncs itself if you login with GitHub, so you're not going to keep having to do this or juggle files around.

In reality it's not that different from juggling around dotfiles and the various configurations that go into other software.

Re: GitHub’s engineering team has moved to Codespaces

#62

Post by toastal »

knoebber wrote: post #46
blueplanet200 wrote: post #3

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

The article specifically says that they support their vim and emacs users by allowing them to SSH in edit code.

No mosh? I've always had some latency issues trying to pull this off on my mobile hotspot or even just in general in SEA.

Re: GitHub’s engineering team has moved to Codespaces

#63

Post by minimaxir »

flurie wrote: post #35

I was curious about the cost. The pricing and compute resources just about correspond to an Azure A series instances, but the ram corresponds better to the v2 series, which is cheaper than v1. I wonder if they're upcharging for v2 machines.

These are also the costs for Teams/Enterprise (who would be willing to pay more); I wonder if they'll release a cheaper/free SKU for individual users.

Re: GitHub’s engineering team has moved to Codespaces

#65

Post by spfzero »

yehudalouis wrote: post #6
zanethomas wrote: post #4

locked-in to visual studio code? no thanks

From the article, it looks like future support for other IDEs is definitely possible: "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 update to our…

Yeah, love the dig at terminal editors with "ed". Anyone using one of those must be stuck back in the 70s on a 16-bit minicomputer terminal.

Re: GitHub’s engineering team has moved to Codespaces

#66

Post by stuff4ben »

systemvoltage wrote: post #29

Is it just me or VSCode is dauntingly complex? There are so many configuration options and I often get lost in it. I've been using Sublime Text for a decade and it has kept the scope creep to a minimum. I've also used JetBrains IDEs and while there is a massive amount of complexity, it is well organized I think. I just get anxiety from launching VSCode, may be it is because of not being familiar with it, I don't know…

I don't use any of the features of VSCode. I just use it as a simple text editor. I'm mainly doing yaml files, bash scripts, and Jenkins pipelines, so I don't need any fancy features. I just "alias vs='code .'" and then "vs" in any directory I have code. It's just a fancy text editor to me that also shows git statuses as well which is nice.

Re: GitHub’s engineering team has moved to Codespaces

#67

Post by theblazehen »

dharmab wrote: post #9
pegler wrote: post #5

Earlier quoted context omitted.

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…

Sounds like terminal editors can be supported but not alternative graphical editors like Sublime or IntelliJ.

Could just use sshfs with any of those editors

Re: GitHub’s engineering team has moved to Codespaces

#68

Post by ansible »

gosukiwi wrote: post #50
verdverm wrote: post #25

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

You can ssh in and run actual editors.

Re: GitHub’s engineering team has moved to Codespaces

#69

Post by lostintangent »

rubyist5eva wrote: post #33

Jetbrains Project support for this would be fantastic.

If you create a Codespace, then install Projector, you can securely forward its server port and then access it from your browser: https://docs.github.com/en/codespaces/developing-in-codespac....

Re: GitHub’s engineering team has moved to Codespaces

#70

Post by fourseventy »

wincent wrote: post #47
blueplanet200 wrote: post #3

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.

Do you have to drag your .vimrc and plugins along every time you set up a new code space? My vim setup is pretty bespoke, it would be annoying to have to set that up every time.
Post reply on HN