Live data from Hacker News

Visual Studio Code 1.7.2

code.visualstudio.com

31–40 of 49 posts

Re: Visual Studio Code 1.7.2

#31
post #20

Earlier quoted context omitted.

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. Here's where you can get a community PPA for VSCode: https://github.com/tagplus5/vscode-ppa

APT and YUM are the standard tbh, the rest is up to the community.

They are no standards.

And both DEBs and RPMs are often distro specific.

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.

Re: Visual Studio Code 1.7.2

#32
post #26

Awesome! 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] [1] https://github.com/Microsoft/vscode/issues/101#issuecomment-...

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.

How can anyone work on an operating system that behaves that's way?

Complain about MacOS we might but at least it doesn't restart without us being able to stop it.

Re: Visual Studio Code 1.7.2

#33

Earlier quoted context omitted.

I'd be willing to send the team a couple pizza's for their work on this... It's my favorite product to ever come out of MS.

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.

Okay, I'd be willing to order two U.S. typically priced large pizzas for the vs code team, assuming a reasonable option is available...

Void where prohibited, quantities limited, some restrictions may apply, batteries not included.

Re: Visual Studio Code 1.7.2

#35
post #32

Earlier quoted context omitted.

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.

How can anyone work on an operating system that behaves that's way? Complain about MacOS we might but at least it doesn't restart without us being able to stop it.

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.

Re: Visual Studio Code 1.7.2

#36
post #32

Earlier quoted context omitted.

How can anyone work on an operating system that behaves that's way? Complain about MacOS we might but at least it doesn't restart without us being able to stop it.

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).

Re: Visual Studio Code 1.7.2

#37
post #2

The speed at which they release updates is at least impressive. Visual Studio Code and Typescript have completely changed the way I look at MS. Kudos to the team.

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.

Re: Visual Studio Code 1.7.2

#39
post #26

Awesome! 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] [1] https://github.com/Microsoft/vscode/issues/101#issuecomment-...

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.

That's the one feature that has me open up Sublime instead if VSCode (for now). I need a scratchpad I can get back to after I reboot.

Hoping they really have it out in the next release.

Re: Visual Studio Code 1.7.2

#40

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.

What do you mean with "scaling resolutions"?
Post reply on HN