Live data from Hacker News

GitHub’s engineering team has moved to Codespaces

github.blog

571–580 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#571

Earlier quoted context omitted.

Go try VSCode remote. These are all solved problems. The extensions run headlessly on the server, and the client does little more than render the interface. Switching between machines is seamless with settings sync, workspace recommended extensions, etc. You won’t find many people who started using VSC remote dev and then abandoned it to go back to local. Once you’ve got it working, which is a pretty easy feat, it’s…

Yes, I am aware. I was responding to this bit: > This seems preferable - the editor runs on your local machine with low latency, but you still run tests on the cloud machine.

Ah I see – apologies, I read your comment too quickly.

Something I miss with remote development is being able to use graphical Git clients like Sublime Merge on my working directory. I don’t want to setup SSHFS just to make that work, and I’m sure performance wouldn’t be great anyway.

Re: GitHub’s engineering team has moved to Codespaces

#572

Earlier quoted context omitted.

Where are we seeing the extend or extinguish with GitHub? It's been 3.5 years and GitHub is just as compatible with git as it has ever been.

You know how they added Github CLI[0], right? There may be a time where you must use Github CLI instead of a "standard" git client to interact with Github projects. That would be the "extinguish" phase. Right now they have embraced and are extending (such as with Github CLI). [0] https://cli.github.com/

If you wish to leverage the advanced features of github, the CLI gives you direct access rather than rolling your own api client. git will always be a first class citizen at GIThub.. but how do you open, close, or comment on PRs with a standard git client?

Edit: The last part came across a bit snarky, but I’m trying to stimulate the thought process. Such as leveraging GitHub Actions to automate all aspects of PRs via gitops instead of using the GitHub client. Many ways to avoid dependence of the CLI!

Re: GitHub’s engineering team has moved to Codespaces

#573
post #358

Serious question: if I were to use this, would Microsoft collect analytics on me (code written, keystrokes, mouse movements, sleep/work schedule, productivity metrics, etc) and monetize that data by using it to build some AI product like Copilot, or build a productivity dashboard so managers can fire people for not being productive enough (like Xsolla did), use it to serve me ads, or do some stupid/irresponsible/unet…

If your employer decides that they need such an analytics dashboard, one that is spying on every keystroke, then they will have one. That one doesn't depend on you working on a laptop, or in a remote environment - the company owns and is administrating that laptop, and they can install everything they regard as necessary.

Therefore the real question is if Codespaces is helping to get your job done; I guess that depends on the complexity and structure of the code, the complexity of the build environment/how you work with the CI environment and how the project is being deployed. I guess that this complex of issues will increasingly dictate how things will get done - if these are too complex, then you are better off with a remote environment.

Re: GitHub’s engineering team has moved to Codespaces

#575

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?

I believe it's data privacy advocate?

Re: GitHub’s engineering team has moved to Codespaces

#577
post #106

Earlier quoted context omitted.

That's not counter intuitive at all: Desktop VS Code is a web app running in chromium.

To be clear, the UI is a web app. But that is serviced by out-of-proc servers written in many different languages (e.g. language servers are usually written in the same language that they service).

In some sense, that's exactly the same as normal web-browsing:

Parts of gmail run in the browser, the rest runs on servers written in many different languages at Google.

Re: GitHub’s engineering team has moved to Codespaces

#578

Earlier quoted context omitted.

Isn’t VS Code Electron based? Same diff at that point

Same regarding the code executed, but not same in that various actions require a round trip to a remote server with attendant latency.

Yes. Though there are a lot of techniques to hide latency.

Re: GitHub’s engineering team has moved to Codespaces

#579

I've had this vision for over a decade and it is awesome to see we are finally making measurable progress towards it. What I'd really like to see is a WebRTC type interface that overlays this to provide some kind of collaborative environment on top of it. I'm thinking of a built in voice chat as well as multi-author editing within the same codespace. Imagine it like pair programming. I'm in FileA.ts and I can see a l…

See Englebart’s mother of all demos. I think he had everything in your first couple paragraphs working in 1968! https://www.youtube.com/watch?v=B6rKUf9DWRI

Did he really? Classic example of demo driven development

Re: GitHub’s engineering team has moved to Codespaces

#580

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, and Microsoft bought them to ensure continuity, because Microsoft was the single largest user.

Yeah they paid 7.5B so they can continue using their favorite web app? This is possibly the most naive take I've read on it that ignores any of the strategic reasons for actually acquiring them.

Post reply on HN