Part mind mapping tool, part wiki, and entirely written in Markdown. Manage your knowledge inside VS Code and publish to the world via GitHub pages (or your favorite static website host).
The incomparable Jessica Kerr drops by with a grab-bag of amazing topics. Understanding software systems, transferring knowledge between devs, building relationships, using VS Code & Docker to code together, observability as a logical extension of TDD, and a whole lot more.
According to the “why does this exist” section of the readme:
When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.
When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a “clean” build, without the Microsoft customizations, which is by default licensed under the MIT license.
This repo exists so that you don’t have to download+build from source. The build scripts in this repo clone Microsoft’s vscode repo, run the build commands, and upload the resulting binaries to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.
The Visual Studio Code license referenced is a short read. You should read it if you use VS Code.
This looks pretty rad. You can:
.diofiles in the Draw.io editor, as xml or both.
.drawio.svgfiles with embedded Draw.io diagrams
- Use an offline version of Draw.io by default
- Configure an online Draw.io URL
- Select a Draw.io theme
May 7th, 2020: A discussion appears on Atom’s forum…
I use Atom for a few years now and was worried back then about the acquisition of Github from Microsoft. And now I read about Github Codespaces, which is powered by Visual Studio Code.
I’m a little concerned about this. Do you still support Atom? And do you support Atom in the future? If there are other opportunities of embedding a Editor or innovating would you also choose VS Code over Atom?
What is the future of Atom? Will you slowly move to VS Code and Atom will be on the support line?
All good questions. There’s been no official (or unofficial, that I’ve seen) response from GitHub just yet.
We’ve been following Atom for years now. Many great developers have put their efforts into the editor. But it’s hard to withstand the gravitational pull of VS Code. Even more so now that Microsoft owns GitHub? 🤔
Find security vulnerabilities in open source npm packages while you code. Receive feedback in-line with your code, such as how many vulnerabilities a package contains that you are importing.
Inspired by Import Cost
GistPad is a Visual Studio Code extension that allows you to manage GitHub Gists entirely within the editor. You can open, create, delete, fork, star and clone gists, and then seamlessly begin editing files as if they were local.
The big idea here is to use gists to seamlessly create your “very own developer library”. The interactive playgrounds is pretty cool, too.
In this episode we talk with Ramya Rao about code editors and language servers. We share our thoughts on which editor we use, why we use it, and why we’d switch. We also discuss what a language server is and why it matters in connecting editors and the languages they support. We also dive into various ways to be effective with VS Code including shortcuts, plugins, and more.
Once the extensions is installed, open a
tsx file and toggle on the sidebar.
Do you remember that endless summer back in ’84? Cruising down the ocean-highway with the top down, the wind in our hair and heads buzzing with neon dreams?
No, I don’t remember it either, but with this experimental theme we can go there.
sshcodeis a CLI to automatically install and run code-server over SSH. It uploads your extensions and settings automatically, so you can seamlessly use remote servers as VS Code hosts.
If you have Chrome installed, it opens the browser in app mode. That means there’s no keybind conflicts, address bar, or indication that you’re coding within a browser. It feels just like native VS Code.
No one likes to spend the day setting up and recreating the config of their text editor of choice. If you use VS Code and Settings Sync you won’t have to. Paige Niedringhaus writes:
This article will show you how to perfectly recreate your Visual Studio Code IDE settings without starting over from scratch and spending hours on it.
When faced with the possibility of losing (or even trying to transfer) my carefully developed VS Code setup to another machine, I knew there had to be a way to do it gracefully. I just knew the solution had to be out there, and so, I asked the internets, and it brought back Settings Sync.
Jonathan Carter, in a deep-dive on the why (and how) behind Live Share:
When we set out to build Visual Studio Live Share, we learned that teams collaborate in very diverse ways, with unique and meaningful perspectives about how it works most effectively for them (e.g. frequency of collaboration, session duration, whether it happens ad-hoc vs. scheduled).
Interesting insights, excellent collaboration feature. 👌
If you’ve been wanting a way to run VS Code as a cloud-IDE, code-server is what you’ve been looking for.
Code-server allows VS Code to run on a remote server making it fully accessible through the browser. … Developers ready to embrace the cloud-based IDE can do so without losing features, or control. This means you can code on your Chromebook, tablet and desktop with a completely synchronized environment. You can spill coffee on your laptop without fear of losing work.
Browser Preview for VS Code enables you to open a real browser preview inside your editor that you can debug. Browser Preview is powered by Chrome Headless, and works by starting a headless Chrome instance in a new process
A syntax theme, icon package, and UI theme for your favorite editor (maybe).
This list is so long it makes me think two things: a) VS Code has an amazingly vibrant ecosystem, or b) the curators of this list aren’t doing enough curatin’. We might find the truth somewhere in the gray space…
Kenneth Reitz, well known in the Python community, creator of Requests, and a former Changelogger has been using VS Code for Python development for several months and is giving it the “should use” status.
Kenneth writes on his personal blog:
I’ve been using Visual Studio Code daily now (for Python development) for about six months — long enough to give it a thorough review. Before, I was using Sublime Text with a few plugins, which worked very well— but, I am continually shocked at just how good VS Code is, in comparison, and I’d like to share with you my observations / opinions…
Ives van Hoorne, creator of CodeSandbox, tweeted this and the attached video has already racked up more than 41.5K views!
… This is not only Monaco, this is VSCode itself directly running in the browser with node shims connected to the APIs of CodeSandbox. This means that we can get Grid View, VSCode Extension support, breadcrumbs + more! I’m so excited by this! #
I’m close to getting VSCode extensions working in their own web worker, then we’ll get things like VIM mode, first class TypeScript support and more! The great thing is that it will work exactly as VSCode, it’s literally the same code base. #
In my endless pursuit of the perfect VS Code setup, I reached out to my colleagues here on the Azure team and asked them to share their favorite extension in their own words. So clear your pallet and breathe in the aromatic flavors of productivity; I am your VS Code Extension Sommelier.
Ives van Hoorne writes on Medium:
Personalizing color schemes is one of the most important things to have in an code editor.
CodeSandbox didn’t have any way to personalize colors in the editor since release, but I’m happy to announce that we do now. The best part is that we were able to reuse a big chunk of logic from VSCode directly and also support any VSCode theme natively in CodeSandbox!
Now you can easily drag and drop your code tabs thanks to the new grid editor layout — complete with horizontal and vertical layout editing. Check the June 2018 release notes for more details.
This thing is packed with features, but the one that really impressed me (and may ultimately lead to me giving VS Code another go) is the Code Lens with inline git blames.
Adds an unobtrusive, customizable, and themable, blame annotation at the end of the current line
So cool! I do fear that it may become more annoying than useful over time, but you never know until you try.
This was inspired by Dawn Labs’ excellent Carbon service, but why leave your editor if you don’t have to, right?
An attempt to use VSCode as a complete note taking application.
This is a port of the SublimeNotebook project, so check that out if you’re a Sublime user.