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.
GitHub’s engineering team has moved to Codespaces
151–160 of 704 posts
Re: GitHub’s engineering team has moved to Codespaces
#152Re: GitHub’s engineering team has moved to Codespaces
#153Ugh, 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 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
#154Earlier 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?
Re: GitHub’s engineering team has moved to Codespaces
#155Earlier 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'…
Re: GitHub’s engineering team has moved to Codespaces
#156Earlier 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.
Re: GitHub’s engineering team has moved to Codespaces
#157Well, if a company pays - then, maybe it's attractive for some. But not for those who love the real power of the real IDE :)
Re: GitHub’s engineering team has moved to Codespaces
#158Earlier 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.
Re: GitHub’s engineering team has moved to Codespaces
#159Earlier 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?