I have been using Windows Insider builds since 2014. It is unique experience for me to see an operating system get developed week by week. Though it is a pain to upgrade (not update) OS every week but it is totally worth my excitement. If I have any resentment I go to feedback app to share my thoughts, and surprisingly I get response too once in while from MS team. MS is not same MS. VS Code is just fraction of what MS has become.
In the next release we'll hopefully have the "hot-exit" behavior like Sublime, where you can close the editor without having to save files, and they're back where you left off when re-opening.
Apparently, the PR for this got merged only 2 weeks ago [1]
Given the recent increase in Windows' no-you-can't-stop-me update restart behavior this seems more important every week, at least on my Windows 10 guinea pig system. Being able to just throw some text into a blank buffer and not lose it in Notepad++ has made that my scratch pad of choice these days.
It actually isn't this way. In the control panel you simply tell the updates to install when you're not using the computer. The only time it forces you to update is when you have ignored or disabled the updates for a period of time.
Yes and no. It'll wait until you're not using the computer to install overnight, when you've been away for a while, whatever.
What it won't do as far as I've seen is allow applications to block the restart if perhaps they contain unsaved data. Your unsaved data is not Windows' problem, and after the restart it won't be yours either - if the app doesn't support hot exit/autosaving of modified buffers/documents then recreating unsaved data will be your problem (but still not Windows' problem).
It really does blow my mind and it isn't at all like their monthly releases are in any way small. Take November's one that they are currently working on for instance here https://github.com/Microsoft/vscode/milestone/30 there is just a bit under 500 different issues that this new release will touch on.
I believe they're in Switzerland, so you may want to be careful with that – or VSCode may become the most expensive software you're using this year :)
IIRC, there was/is a frequent stream of pizzas being delivered over the German-Swiss border because of the price difference – it got so much that they actually started to set up customs checks.
The problem with this is that if they support apt, where should it stop ? should they support portage, pacman, homebrew, Nix, Guix, yum, dpkg ?
I don't think it is Microsoft's job to provide packages for every manager. They should make an executable and then anyone who uses a package manager can package the program.
Linux releases should be done source only making it as easy as possible for packagers to compile using libraries present on the system; or using a tool like AppImage and packaging everything yourself.
I have this and Sublime installed...until the editor gets rid of fuzzy fonts when scaling resolutions, I unfortunately have to stick to Sublime even though I reaaaaaaaaaaaaally like VS Code.
I have a 4k screen, but like to set resolution scaling to 150% on Windows. MacOS also does this for the retina displays. It looks fine for the most parts, and fonts render fantastically with Sublime but VSCode fonts in the editor are blurry and make it harder on the eyes for reading.
The HTML Audio and Video support is probably all not used in Code. However I guess it could be hard to compile chromium (and electron) without these, if they didn't invest the additional effort to put them behind a compile flag.
Two main issues combined to cause the NPM problems: NPM didn't cache 404 responses, so they were much more expensive than normal fetches, and VS Code issued way too many requests which resulted in 404s.
Both have been addressed -- NPM handles 404s better now, and VS Code will no longer request packages which don't exist (by downloading the registry package once). Either fix would have be sufficient, but having both is better.
Considering they've been working together with NPM since the previous recovery build, I highly doubt they would have released this unless both parties were really sure this will cause no problems.
Visual Studio Code and Typescript have completely changed the way I look at MS.
Kudos to the team.