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

GitHub Codespaces

github.com

Post reply on HN
Print view View original

91–100 of 619 posts

Re: GitHub Codespaces

#91

Post by skrtskrt »

swagonomixxx wrote: post #60

This is pretty epic. VS Code has proven itself to be one of the best (if not the best) and feature-complete editor out there. It's basically an IDE of a ton of languages at this point, and it's completely free. Integrating it with GH is a no-brainer move from Microsoft's standpoint, to increase market share even further with more seamless integration. If they're able to do setup for Python, Go, Ruby, and JavaScript p…

While VS Code is definitely good in general, and first choice for languages like JavaScript, I find it really hard to compare it to JetBrains PyCharm and GoLand (understanding GoLand has no free version).

The debugging and refactoring experiences for Go and Python in VSCode feel slow, awkward to set up and configure and just generally tacked-on.

I have gotten the PyCharm professional and GoLand licensed through my employer but I will 100% be paying for them out of my own pocket if I ever lose that.

Re: GitHub Codespaces

#92

Post by dmacewen »

michaelmior wrote: post #69
dmacewen wrote: post #22

I wonder if it's usable from an iPad. I haven't tried an online ide before, but if it works well it could be a great mobile development tool. It would be awesome if this could be setup as a backend for vim as well. Given how well Coc.vim integrates with VSCode tooling, I'm cautiously optimistic.

What do you mean by "a backend for vim"? I use vim almost exclusively for coding but I'm not really sure what you mean here.

Backend may have been the wrong word, but they mention being able to connect to your codespace from VSCode running on your computer. It would be cool if you could connect to your codespace from vim running on your computer in the same way.

Re: GitHub Codespaces

#93

Post by dmacewen »

mcolyer wrote: post #66
dmacewen wrote: post #22

I wonder if it's usable from an iPad. I haven't tried an online ide before, but if it works well it could be a great mobile development tool. It would be awesome if this could be setup as a backend for vim as well. Given how well Coc.vim integrates with VSCode tooling, I'm cautiously optimistic.

That's correct it's usable from an iPad during the beta. There are a few known issues but we're planning on addressing those so that we can support this workflow (I work as the product lead on Codespaces).

Wow, great to hear!

Re: GitHub Codespaces

#94

Post by saagarjha »

mcolyer wrote: post #66
dmacewen wrote: post #22

I wonder if it's usable from an iPad. I haven't tried an online ide before, but if it works well it could be a great mobile development tool. It would be awesome if this could be setup as a backend for vim as well. Given how well Coc.vim integrates with VSCode tooling, I'm cautiously optimistic.

That's correct it's usable from an iPad during the beta. There are a few known issues but we're planning on addressing those so that we can support this workflow (I work as the product lead on Codespaces).

Does it work with the software keyboard? I seem to recall Monaco not really supporting mobile.

Re: GitHub Codespaces

#95

Post by mempko »

kick wrote: post #39
sandstrom wrote: post #34

Earlier quoted context omitted.

The people at Github that used to be paid to work on Atom may be the ones that built this :)

Wouldn't be my guess, personally: https://github.com/atom

yeah, not much action there. Vim gets much more action per day.

Re: GitHub Codespaces

#96

Post by alberth »

design wrote: post #81
dawson wrote: post #38

Earlier quoted context omitted.

This tweet from GitHub's lead designer would suggest so! https://twitter.com/notdetails/status/1258070699165585410 ... also this tweet from another GitHub product designer https://twitter.com/mschoening/status/1258069269260038144

Hey, the first tweet is mine. Codespaces work pretty great on an iPad. We're going to be making improvements to the experience here as we get to GA but we know it's a scenario everyone is really excited about.

Is the screenshot of Codedpaces from your iPad or macOS? Because that looks a lot like safari on macOS.

https://mobile.twitter.com/notdetails/status/125807069916558...

Re: GitHub Codespaces

#97

Post by IAmLiterallyAB »

tomnipotent wrote: post #33
underdeserver wrote: post #15

I like how they say that if you don't want to develop in a browser, you can connect VS Code. You're still developing in a browser. Still a great IDE though.

> You're still developing in a browser. How so? Node/Electron != browser, though I see how the whole HTML/JS/CSS thing can be confusing.

It's a browser without an address bar.

Re: GitHub Codespaces

#98

Post by dvtrn »

mcolyer wrote: post #66
dmacewen wrote: post #22

I wonder if it's usable from an iPad. I haven't tried an online ide before, but if it works well it could be a great mobile development tool. It would be awesome if this could be setup as a backend for vim as well. Given how well Coc.vim integrates with VSCode tooling, I'm cautiously optimistic.

That's correct it's usable from an iPad during the beta. There are a few known issues but we're planning on addressing those so that we can support this workflow (I work as the product lead on Codespaces).

Super excited to hear this, I had the exact same question reading the page. Any chance you'd be willing to slip us a peak on when we could reasonably (even a Qx ballpark) on when Beta begins?

Re: GitHub Codespaces

#99

Post by searchableguy »

saagarjha wrote: post #87
colordrops wrote: post #76

Earlier quoted context omitted.

Let's just hope they don't only maintain this online editor and deprecate the desktop install.

That sounds quite unlikely.

Doesn't to me (they might not deprecate it but they will simply stop putting resources into it at which point it turns into maintenance mode). As another posted pointed out the Facebook links, companies would love remote IDE tooling hosted on their premise so it can be an easy way to remove overhead on onboarding and tighten security more.

For monorepos, it might work pretty well.

Re: GitHub Codespaces

#100

Post by [deleted] »

onionisafruit wrote: post #70
tomnipotent wrote: post #33

Earlier quoted context omitted.

> You're still developing in a browser. How so? Node/Electron != browser, though I see how the whole HTML/JS/CSS thing can be confusing.

I think it’s saying you’re still using chrome under the covers when you use electron apps.

[deleted]
Post reply on HN