I'm not a developer but I thought consistent development environments was something that containers was supposed to solve ?
GitHub’s engineering team has moved to Codespaces
161–170 of 704 posts
Re: GitHub’s engineering team has moved to Codespaces
#162Earlier quoted context omitted.
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?
The difference is that you don't pay a monthly subscription to use a garbage collector.
The garbage collector should pay _me_ to use it.
Re: GitHub’s engineering team has moved to Codespaces
#163Now it will be pretty easy to bring back those pesky remote workers to the offices. They will just tweak some code on the backend and poof , the latency of your home connection skyrockets to the point of typing becoming impossible. Luckily there won’t be such an issue with the office internet! I guess we’ll have to come back to the office to keep being productive in this web-based IDE :^)
I have some of the worst home wifi possible, and have been comfortably developing from Codespaces for over 6 months :) Editing happens locally in the client (and is synced to the service in parallel), and so you shouldn’t notice any latency when typing.
Is this true even when you are using Emacs/Vim? I know vscode has server mode and emacs has `emacs --daemon`.
Re: GitHub’s engineering team has moved to Codespaces
#164Ugh, 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…
> 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.
Bingo. The inevitable rug pull is going to be very, very expensive/catastrophic for a lot of people (though, profitable if you understand the underlying systems).
Re: GitHub’s engineering team has moved to Codespaces
#165I would quit so fast if my company forced me to use a web IDE.
GitHub isn't forcing anybody to use a web IDE. The most broadly used access interface is VSCode. Then there are heretics like me who choose to ssh in so we can use Vim. This is described in the article.
Can you install RDP/VNC and just remote into it like that? Then get sudo access and install whatever you want on it?
Re: GitHub’s engineering team has moved to Codespaces
#166I see a bright future for this on some types of teams.
How does the billing work when I'm not using Codespaces? Does the VM stop automatically after some time idling or do I have to manually pause it to stop billing?
Re: GitHub’s engineering team has moved to Codespaces
#167> CPU up to 32 cores
> Memory up to 64 Gb
Great, barely enough to develop my new Electron app.
Re: GitHub’s engineering team has moved to Codespaces
#168Earlier quoted context omitted.
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?
The difference is that you don't pay a monthly subscription to use a garbage collector.
I bet somewhere you just gave a Lang Developer a monetization idea...
This will be coming to a cloud service near you
Re: GitHub’s engineering team has moved to Codespaces
#169Earlier quoted context omitted.
I'm in the GitHub Codespaces personal beta: counterintuitively, the UI/UX of Codespaces is as performant as VS Code on the desktop.
Isn’t VS Code Electron based? Same diff at that point
Same regarding the code executed, but not same in that various actions require a round trip to a remote server with attendant latency.
Re: GitHub’s engineering team has moved to Codespaces
#170Ugh, 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…
Given the whole outrage over Apple taking advantage of customers' willingness to hand over control of their phones to them, I hope folks can see the parallels here and reject this. At this point Microsoft's strategy around GitHub, VS Code, Copilot, etc. should be pretty obvious, and we should all be running for the hills.
Some could even call it Embrace, Extend, Extinguish...
hmmmm.......