dev VS Visual Studio Code

They aren't using code spaces or github.dev I believe. They are actually using "Edit in place" which is adjacent to those options. The first image in this link might help:

You are mostly right, but the "remote" aspect comes from the fact that https://github.dev/ can open any random repository (e.g. go to this LLVM README file and then hit the "github.dev" in the dropdown menu for edit). Nothing gets downloaded to your computer and happens on the cloud. You are editing a remote repository on a remote computer.

You should know with great power comes with greater bill. You can use https://github.dev/github/dev, vscode.dev, github1s.com to WRITE and READ source code, but can't compile nor run. If you want to run, you will need Github Codespace which costs money.

Checkout "github.dev" (which is based on vscode.dev)

last week i stumbled across vscode.dev and github.dev which are web versions of my beloved editor. Of course there is no terminal available, which made me curious? is ther a way or service that lets you use a linux container to remote into and use vscode on the go?

TIP: If your source code is on GitHub, and you just need to show the source code, you can use github.dev, a lightweight, browser-based editor (based on VSCode) you can access by replacing .com with .dev when typing the repository URL. It even supports some extensions such as the brilliant CodeTour, which is great for showing code in a guided way throughout your session.

I am using codespaces (github.dev) as the IDE.

I can't believe I am just finding out about https://github.dev a vscode interface for any github repo. For example: https://github.dev/expo/expo/

Add a custom search engine in Chrome and you got yourself a quick shortcut to opening any repo in github dev. In the past I would clone repo then open with vs code to monkey around. Now its CMD+L , 'gd expo/expo' to open https://github.dev/expo/expo/

Instructions for adding custom omniBar search shortcuts: https://zapier.com/blog/add-search-engine-to-chrome/

Just in case this isn't common knowledge: You can hit the period (.) key while on any github page to launch a vscode in browser (uses https://github.dev/).

I'm using Silverblue 39 for about 2 month coming from NixOS Unstable. It's working very well for me. I have some packages layered like Nvidia and fish shell and https://github.com/CheariX/silverblue-akmods-keys for AKMODS modules work with secure boot. Things like neovim, pyright, helix, starship, LSPs and CLI applications I install with brew (brew.sh). For desktop things I use Flatpak.

I had a problem with some Flatpak applications (like Steam and Discord) and brew because brew puts its folder in the $PATH before the default ones (/usr/bin ...) and those Flatpak applications tried to use SSL keys from brew instead of the system ones. I just changed the order of the $PATH to make brew bin path to be after ther system ones.

For VSCode I'm not using the Flatpak I'm using the tarball one I just extract in ~/applications and symlink the code binary in the ~/.local/bin. It's working well, I don't have problem with VSCode not executing LSPs and lint things. The only problem is VSCode from tarball cannot updates itself, so I need to download the newer version and extract to ~/applications. There is this VSCode CLI version (https://code.visualstudio.com/docs/?dv=linux64cli) but I was not able to make it use the wayland backend.

Explore the official VS Code documentation on the Visual Studio Code website for in-depth guides, tutorials, and reference materials.

It's a lot, but the VS Code docs have thought about Extraneous Cognitive Load and created written guides, video guides, reference docs and more!

VSCode has a long history of not working well with Unity, so they deprecated it.

> Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux.