Live data from Hacker News

GitHub’s engineering team has moved to Codespaces

github.blog

151–160 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#151

Earlier quoted context omitted.

jamstack is very fucked up to me, glad I'm not going crazy. you basically offload EVERYTHING to 3rd parties.

There's nothing about jamstack that requires you to use third-parties (except the CDN part, I guess, but that's just a mirror). You could just as easily host your own CMS and database and call out to it the same way. It's just that like auth, logging, etc, CDNs have been neatly abstracted out and service-ified in such a way that it's often more economical to go third-party. But that choice is orthogonal to jamstack.

I agree on that, and was going to add that, to be fair to the stack. But the reality is, while that's doable, most people just use third-party services, at least that's my experience.

Re: GitHub’s engineering team has moved to Codespaces

#153

Ugh, now not only you don't own your code ( ahem copilot cough ) you also don't own the tools to develop code. The direction the web is taking is worrisome. The issue is not so much senior devs, but new devs. If they start off with things like that, there' so much magic under the hood, they won't understand how anything works. They don't understand they don't own shit until it's too late. I remember when I first saw…

The same thing was said about every programming abstraction to ever be introduced. How do we expect people to build memory-efficient applications when they become reliant on a garbage collector?

I've never seen a company collapse because their garbage collector posted an Our Incredible Journey™ blog post and then shut down a week later.

I have seen multiple companies collapse because the proprietary Backend-as-a-Service they built their sand castle on top of pulled a vanishing act, however.

Re: GitHub’s engineering team has moved to Codespaces

#154
post #127
post #38

Earlier quoted context omitted.

(googler, opinions are my own). Google allows for normal desktop IDEs, plus having a web based one. The funny thing is, many people move to the web based one because it is so good. But Google is also unique in how piper/citc[0] (our source control) works. It's effectively designed for web/cloud based style development, so the workflow for web based dev and desktop dev are effectively the same. So web dev can work, bu…

Interesting, can you elaborate a bit on "cloud-based" development vs for example a traditional workflow of git and a central repo?

Should've read the entire post first. o\

Re: GitHub’s engineering team has moved to Codespaces

#155
post #144

Earlier quoted context omitted.

The difference is that you don't pay a monthly subscription to use a garbage collector.

There's two things happening in this post: 1. Development environments are running on Kubernetes, and VS Code is remoting into them. You don't have to pay a monthly subscription for that. VS Code remoting is free-as-in-beer and Kubernetes is free-as-in-speech. https://code.visualstudio.com/docs/azure/kubernetes 2. The actual Kubernetes hosting is the product "GitHub Codespaces" running on Azure. GitHub certainly isn'…

Microsoft probably does internal billing here, right?

Re: GitHub’s engineering team has moved to Codespaces

#156

Earlier quoted context omitted.

The difference is that you don't pay a monthly subscription to use a garbage collector.

Garbage-collection-as-a-service would get a ton of venture capital though.

Oh wow, AR/VR mark/sweep applications! Those VR rooms get messy, who is going to clean them up?

Re: GitHub’s engineering team has moved to Codespaces

#158

Earlier quoted context omitted.

jamstack is very fucked up to me, glad I'm not going crazy. you basically offload EVERYTHING to 3rd parties.

There's nothing about jamstack that requires you to use third-parties (except the CDN part, I guess, but that's just a mirror). You could just as easily host your own CMS and database and call out to it the same way. It's just that like auth, logging, etc, CDNs have been neatly abstracted out and service-ified in such a way that it's often more economical to go third-party. But that choice is orthogonal to jamstack.

jamstack certainly presents itself first and foremost as "use third party services".

Re: GitHub’s engineering team has moved to Codespaces

#159
post #19

Earlier quoted context omitted.

I am wary of requiring an internet connection in order to develop, but there seem to be more and more advantages to using something like Codespaces. The article describes using pretty much any IDE, so they are just offloading the setup and running of the development environment to the cloud while letting you run your preferred IDE locally.

I can see how a web based IDE speeds up on boarding and reduces the friction in support and collaboration. But I wonder if it reduces the skills engineers develop over time?

What skills would developers really lose? Speeding up boarding seems like a win, not many skills are developed imo trying to set up you personal dev environment. It's mostly just frustrating when a company's tools don't work well on your machine.

Re: GitHub’s engineering team has moved to Codespaces

#160

Earlier quoted context omitted.

The difference is that you don't pay a monthly subscription to use a garbage collector.

Garbage-collection-as-a-service would get a ton of venture capital though.

Hahaha cloud-based garbage collection. Made me giggle.
Post reply on HN