From official blog https://code.visualstudio.com/blogs/2021/10/20/vscode-dev More on reddit.com

This saves me a lot of time as a maintainer in some cases where otherwise I'd have to add the fork as a remote and then check it out locally · Hoping that they'll add support for terminals as well at some point though I suspect maybe that'll forever be reserved for Codespaces More on news.ycombinator.com

When you begin working on larger projects you'll want to commit often in case you break something and it also makes Quality Assurance's (QA) life easier since they will see what you did to the code, and you qill have multiple tasks. Commiting all at once is big nono. No need to push everything at once. You can do add commit multiple times without pushing. For example, once you set up the backend for a webpage on a site, you might want to "git add xfile.js" > "git commit -m "did somestuff", and then when you go to the next one, same thing. To get some practice, find an open source project and contribute to it. Go to github: Fork open source Clone to your machine Edit. Play around with it. Push. Pull request. More on reddit.com

As I see it, vscode.dev is just an online editor with no possibility for running code. Perhaps I have misunderstood its usage. GitHub Codespaces is a rather complete programming environment where you run a VS Code instance in what is probably a Linux virtual machine. There is not much I can do on my PC, which I can't also do in GitHub Codespaces. More on reddit.com