Hello! Blog post author here. Wanted to quickly comment on how we support offline folks or those working on an unstable connection! The short version: we publish a container image into the GitHub Container Registry that closely tracks github/github’s devcontainer image. Folks can pull and use locally with VSCode remote containers or run directly in Docker. The github/github checkout is local in this case and mounted into the container.
GitHub’s engineering team has moved to Codespaces
251–260 of 704 posts
Re: GitHub’s engineering team has moved to Codespaces
#252Maybe they should have used Nix to get a dev environment that is identical for everyone... but that would be too easy. The future is long term probably in the web, I'm just not sure we are there yet.
Buy a Cachix subscription and now the org can build once on the local dev's machine, push to the service, then other users and machines can download & run anywhere the reproducible 'apps' on local dev machines, CI, and even production. CI can even build and push the architectures that aren't specific to your local machine to cover just about everything.
This is what we do at work, and it's working great for us.
GitHub's approach seems utterly ridiculous, especially given that I've seen colleagues prevented from working because their Internet connection at some point ran through a part of the world that was sanctioned by Western governments.
Developer, it appears you are somewhere near Crimea! NO EDITOR FOR YOU!
Re: GitHub’s engineering team has moved to Codespaces
#253> CPU up to 32 cores > Memory up to 64 Gb Great, barely enough to develop my new Electron app.
If your new app needs so much resources, I'm sorry to tell you, but it's not Electron. It's your app.
Re: GitHub’s engineering team has moved to Codespaces
#254It sounds like this use case is for developer's who buy laptops expecting them to act like desktops and then realize their mistake.
Maybe the cheaper, simpler, option is just to buy a performant desktop for less $$$ than has wall current and the space for RAM and heat dissipation.
Re: GitHub’s engineering team has moved to Codespaces
#255Ugh, 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…
It's amazing how github is not open source, the biggest host of open source software is closed source?
Re: GitHub’s engineering team has moved to Codespaces
#256Re: GitHub’s engineering team has moved to Codespaces
#257Earlier quoted context omitted.
It's funny because we told people not to trust big companies, they tell us we are paranoid, they do it, they pay the price for it, then they say we were right, then they do it again. MS changed. Google changed. Apple changed. Why do one expect github to never turn evil ? Haven't learned enough from history ? Don't let them control your entire stack! Don't let anybody control the entire of anything. There is a differe…
It's over once we don't have control of the compilers. Look at the iPhone.
give up so easy.
Re: GitHub’s engineering team has moved to Codespaces
#258Assuming it auto detects idle time? Could be a good alternative to buying new MacBook
Yes it does detect. My environment is usually stopped after a break or a boring meeting.
Re: GitHub’s engineering team has moved to Codespaces
#259I've developed on a remote server for about 8 years now. It started when I was a contractor and my machine was simply too slow to run the project I was assigned. I did not have the money for a new laptop, but I could afford the ~55/month for a dedicated server with 32GB and 4cores. I have worked that way ever since. I've been fortunate enough to work at companies that run their own VM infrastructure which allow me to…
If you work from a park how do you manage your latency/connectivity to a remote server? It must get annoying fast when a pigeon flies over causing your hotspot to cut out.
Re: GitHub’s engineering team has moved to Codespaces
#260Earlier quoted context omitted.
> And things like the Rails monolith that GitHub's main service is, have a tendency of being rude to a dev's laptop FUD. Everything is neatly handled by rvm (or rbenv) and bundler. You can even use gemsets if you want to be really anal about it. It all goes in version-controlled user directories. I keep my main Mac machine, my work Windows machine, and the production Linux boxes all running the same versioned stack j…
What do you mean FUD? Maybe you've got your own way of doing things that works well so far for you with your current projects, but a ton of people don't live with the same experience, and when they do reach a comfortable spot, it's only comfortable until they move to a new set of projects or company.
Codespaces doesn't magically solve that problem. You have to put in the work and ongoing maintenance effort either way.