
With these programming languages, you'll get the "Good" experience plus rich single file completions, semantic highlighting, syntax errors, and more.
Better: The TypeScript, JavaScript, and Python experiences are all powered by language services that run natively in the browser. Using a Tree-sitter syntax tree, we're able to provide additional experiences such as Outline/Go to Symbol and Symbol Search for popular languages such as C/C++, C#, Java, PHP, Rust, and Go. Good: For most programming languages, v gives you code syntax colorization, text-based completions, and bracket pair colorization. Variability among those services results in these three levels of VS Code for the Web experiences listed by Dias: The same thing happens with desktop versions, but those language services (and compilers) are designed to work with local resources like a file system, runtime and compute environment.
Your mileage may vary with other experiences like code editing and navigation, which in VS Code are driven by programming language services that provide language-specific functionality. While that only works for a couple of modern browsers now - Edge and Chrome - those using non-supported browsers can still access local files using browser tooling. You can upload/download files (and even store them in the cloud using the Files app), as well as open repositories remotely with the built-in GitHub Repositories extension.
Edit your code on lower powered machines like Chromebooks, where you can't (easily) install VS Code.
Build client-side HTML, JavaScript, and CSS applications in conjunction with the browser tools for debugging.
Even if you are on a restricted machine where you cannot install the full VS Code, you may still be able to use v to view and edit local files.
Quickly take notes (and preview!) in Markdown. There is local machine file access, however, enabled by the File System Access API.