Live data from Hacker News

GitHub’s engineering team has moved to Codespaces

github.blog

491–500 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#491
Huh, so there we are again:

* you write code in VSCode (developed by Microsoft)

* using Codespaces (created by Microsoft)

* in TypeScript (developed by Microsoft)

* downloading libraries from NPM (owned by Microsoft)

* pushing your code to Github (owned by Microsoft)

* to run it on Azure (by Microsoft)

and on top of that you read email about the launch of a new feature in Outlook and celebrate it with your colleagues on Microsoft Teams...

Re: GitHub’s engineering team has moved to Codespaces

#492
post #229

Earlier quoted context omitted.

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.

I did not understand that part. Every heavy Emacs or vim user have its own customizations of editor. How does it work with shared image?

The codespaces can have their own dotfiles.

Re: GitHub’s engineering team has moved to Codespaces

#493
If I understand correctly, this is similar to Google's CitC (clients in the cloud) [1].

According to the article, Codespaces supports non-IDE users by allowing ssh. CitC supports non-IDE users with a network file system. This seems preferable - the editor runs on your local machine with low latency, but you still run tests on the cloud machine.

I wonder if Github supports this workflow, e.g. by configuring sshd to allow sshfs/sftp access.

[1] https://cacm.acm.org/magazines/2016/7/204032-why-google-stor...

Re: GitHub’s engineering team has moved to Codespaces

#495

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?

Data Protection Authority

Re: GitHub’s engineering team has moved to Codespaces

#496
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 a business is paying for this product, then THEY (not you) are the customer. And in that context - yes, Microsoft may be asked or build a product for managers to manage their workforce, particularly if remote. This could involve presence tracking, engagement tracking (ie, do you open alerts / read your bug reports) etc. One approach would be to monitor what management considers productive / successful employees an…

We can’t create enough material machines for everyone that wants to code to code.

If that’s dystopian, wait until you hear about your impending natural death.

I can sit by a tree and work on my sci-fi space opera for hours.

I feel really sorry for people who are so addicted to technology they think the entire species should surrender its agency to that pipeline.

A hardware machine has known operational limits. No amount of delusion about coding and games means it’s anything more than a dopamine buzz (if it can be described as such scientifically as dopamine floods then it is).

None of us are resolving or answering questions about reality. We’re just masturbating a chemical delusion.

Who knows? Maybe organic machines are even cooler and we can program organic matter via chemical and electrical manipulation.

But let’s have another go around writing x86 code.

Wow. How clever. There’s a new skin to put on a MySpace clone in one of us somewhere!

Re: GitHub’s engineering team has moved to Codespaces

#497
post #462

Earlier quoted context omitted.

That is somewhat fair - there aren't great alternatives to migrate issues and the like to today. But all of those bits of metadata are easy to pull out of the service via API hooks. If someone wanted to start a serious competitor to github that shares the same basic data model it'd be pretty trivial to write up migration aides. I don't disbelieve that it's possible for microsoft to severely restrict these - but entir…

> If someone wanted to start a serious competitor to github that shares the same basic data model it'd be pretty trivial to write up migration aides. Like Gitlab? I assumed Gitlab would dominate after the MS purchase of Github, but I was incorrect that people wouldn't want to trust their data and personal projects to the epic abusers of privacy that is Microsoft.

Well I don't think the personal projects are really a significant factor in terms of where MS's paychecks are coming from - they care more about the commercial subscribers. And, speaking as someone employed at a commercial subscriber, objecting to continuing to use github due to the microsoft acquisition when we use office for pretty much all document production is going to be a pretty hard argument.

Re: GitHub’s engineering team has moved to Codespaces

#498
post #493

If I understand correctly, this is similar to Google's CitC (clients in the cloud) [1]. According to the article, Codespaces supports non-IDE users by allowing ssh. CitC supports non-IDE users with a network file system. This seems preferable - the editor runs on your local machine with low latency, but you still run tests on the cloud machine. I wonder if Github supports this workflow, e.g. by configuring sshd to al…

The problem I see with a remote filesystem is that you’ll still need tools for editor integrations - language servers, formatters, linters, etc.

Sure, you can install those locally too, but by then you are losing many of the benefits of a cloud environment.

Re: GitHub’s engineering team has moved to Codespaces

#499
post #375

Interestingly, the intro docs specifically recommend using Chromium for Codespaces: > For the best experience with Codespaces, we recommend using a Chromium-based browser, like Google Chrome or Microsoft Edge. (from https://docs.github.com/en/codespaces/developing-in-codespac... ) Makes sense coming from Microsoft, but it'll be fun to see if/how that affects the ongoing Chromium/Safari battles (and Firefox, to a less…

This is because it’s based around VS Code, which is an Electron app, which uses Chromium. In short they never tested it outside it because they never had to. Only now it’s become available as a “web app” with a URL.

They’ve put a ton of work into making VSCode browser independent because of Codespaces. It now works in Mobile Safari pretty well, as well as Firefox.

Re: GitHub’s engineering team has moved to Codespaces

#500
From the article:

> The GitHub.com repository is almost 13 GB on disk; simply cloning the repository takes 20 minutes.

Their problem seems to be mainly this. Which I'm surprised that they don't fix, but invent a workaround for. Deleting/rewriting a git repo's history is not impossible and often necessary for these kinds of cases.

Post reply on HN