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

661–670 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#661

Post by JoyrexJ9 »

reggieband wrote: post #382
dynamicwebpaige wrote: post #356

Earlier quoted context omitted.

> _I'm thinking of a built in voice chat as well as multi-author editing within the same Codespace._ You should try Live Share! VS Code Live Share enables you to collaboratively edit and debug with others in real time, regardless what programming languages you're using or app types you're building. It also supports voice chat: https://marketplace.visualstudio.com/items?itemName=MS-vsliv...

This isn't exactly what I'm proposing since it seems to be based around sharing my code. I may be misunderstanding the documentation and examples however. Live Share appears to be me inviting people to connect to my personal session. I see a codespace as a shared destination. It lives independently of any individual. I can hop in and out whenever I want and it continues to live. To expand on this, it reminds me of ho…

There is 'Discussions' for this, which you can enable per repo on GitHub, and have a sort of chat / forum as part of the repo

Re: GitHub’s engineering team has moved to Codespaces

#662

Post by maccard »

gmueckl wrote: post #631
maccard wrote: post #532

Earlier quoted context omitted.

So to be clear, the proof the GitHub is extending is a hypothetical example of an incomplete api that is not based on an open standard?

I didn't want to prove anything. I just pointed out what is possible.

Sorry, I misread the username and assumed you were the commentor I replied to. Yes, these things are _possible_ but there is no evidence or indication that they are happening with Github.

Re: GitHub’s engineering team has moved to Codespaces

#663

Post by maccard »

pdpi wrote: post #584
maccard wrote: post #530

Earlier quoted context omitted.

By that logic any proprietary product that provides an interface with an open source tool is guilty. I think accusing MS of EEE in this case is a huge stretch; GitHub is a commercial product that uses a popular open source tool with 100% compatibility (that I'm aware of) and actively participates in the development and features of that tool. When Ms start implementing extensions to git that only work with GitHub, we…

I can’t think of a single person I’ve worked with in the last 10 years who understands the difference between vanilla git and GitHub. Nobody really understands why pull requests are named that way, or that it’s possible to have very different workflows to what GitHub offers. I don’t know that this is the result of a deliberate strategy by GitHub, but by any metric the extend step is a resounding success.

> I can’t think of a single person I’ve worked with in the last 10 years who understands the difference between vanilla git and GitHub.

If not one developer in a decade can tell the difference between a source control hosting service and a tool they use, that's not really GitHub's problem. This is the same as my parents not konwing that "facebook" isn't the internet.

> Nobody really understands why pull requests are named that way,

Sure they do, the answer is one google search away on the largest Q&A forum for programmers [0]. it was the first google hit for "why are pull requests called pull requests"

> or that it’s possible to have very different workflows to what GitHub offers.

Maybe inside your circle, but plenty of people are aware of different workflows. Some of the largest open source projects in the world exist on github and don't use the pull request workflow (linux kernel, firefox, chromium off the top of my head).

[0] https://stackoverflow.com/questions/14817051/why-does-github...

Re: GitHub’s engineering team has moved to Codespaces

#664

Post by raxxorrax »

jrochkind1 wrote: post #490
zamalek wrote: post #207

Earlier quoted context omitted.

I've been playing around with a homegrown version of this. It's really not that hard: just set up a docker context to your home lab server and use VSCode remote containers. I've been able to remove WSL from my PC: Docker desktop was gouging itself on resources. I can now also shut down my desktop and continue exactly where I was on my laptop, and visa-versa. I don't have to pull WIP commits back and forth between the…

oh right, my home lab server, that must be around here somewhere...

I pay 30$ a month for a server (yes, a virtual one, if you want docker, you have to pay a bit more) with org-domain and tls cert. I would recommend that to every developer. Yes, some administrative work is required but that is also a valuable learning experience. You would own all the tools that you need to develop efficiently.

Personally I use Gitea, which should be usable by someone used to Github. I don't switch workspaces too often, but I am sure some tools are available.

Re: GitHub’s engineering team has moved to Codespaces

#665

Post by blacktriangle »

maccard wrote: post #644
fartcannon wrote: post #583

Earlier quoted context omitted.

there's never a stretch with Microsoft. It is always, and has always been the same play. You can make excuses all you like, but in the end they will attemtp to embrace, extend and extinguish all competition.

Wheh they show any signs of extending git, or extinguishing any other open source competitors, I will be standing there with you calling them out. Until then, they're developing an excellent product that people want to use, built with open tooling

Those who don't study history are doomed to repeat it.

Re: GitHub’s engineering team has moved to Codespaces

#666

Post by DaiPlusPlus »

vbezhenar wrote: post #651
DaiPlusPlus wrote: post #648

Earlier quoted context omitted.

As long as there's more demand than supply for SWE workers, something like that would never become the norm. All of the dystopic news stories of WFH employees being subject to monitoring are invariably from fungible employees.

I often read on HN that it's a norm for US employers to install spying software on developers computers. I don't see how is it different. I would try to avoid from working in such a companies, because I don't feel secure knowing that someone is spying on me.

> I often read on HN that it's a norm for US employers to install spying software on developers computers.

I haven't heard of this happening at all.

Whereas it is commonplace for people to use time-tracking software (like Toggl, RescueTime, etc) - and it is also not-uncommon for companies to require employees to use such software (software-eng or otherwise) for the purposes of reporting their time/hours/what-they're-doing, they all have web-based UIs for doing data-entry: which is definitely not the same thing as installing monitoring software on an employees' own personal hardware with or without their informed consent and it being a condition of employment.

I think people are getting terms-conflated and using overloaded terms with negative connotations: "time tracking software" which does active-software-application-window-tracking for the benefit of the direct user can easily be mischaracterized as "monitoring software".

Re: GitHub’s engineering team has moved to Codespaces

#667

Post by gmueckl »

maccard wrote: post #662
gmueckl wrote: post #631

Earlier quoted context omitted.

I didn't want to prove anything. I just pointed out what is possible.

Sorry, I misread the username and assumed you were the commentor I replied to. Yes, these things are _possible_ but there is no evidence or indication that they are happening with Github.

I agree that there are no signs at the moment. Companies change over time, so a certain risk - however small - is present, as with all 3rd party services.

Re: GitHub’s engineering team has moved to Codespaces

#668

Post by nmfisher »

TechBro8615 wrote: post #544
hamandcheese wrote: post #498

Earlier quoted context omitted.

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.

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…

This is what I've started doing, and I'm definitely a life-long convert.

I still experience a few glitches (extensions randomly stop working, Intellisense sometimes dies, and auto-detecting architecture for launching mobile apps sometimes fails) but I'm sure those will be ironed out.

Re: GitHub’s engineering team has moved to Codespaces

#669

Post by _pmf_ »

bogwog wrote: 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…

Of course.

Re: GitHub’s engineering team has moved to Codespaces

#670

Post by raxxorrax »

baby wrote: post #621
bogwog wrote: 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…

Top comments always have to be so negative every time there’s something cool on the front page…

Look how tech is employed against lower wage workers. It is a good idea to be extremely vigilant about anything "reporting". I think people working in tech have a responsibility to not behave like 14-year old fangirls.
Post reply on HN