Visual Studio Code 1.8 • Hacker News Board

Re: Visual Studio Code 1.8

#21

Post by amadeusw » Wed, Dec 14, 2016, 9:56 PM UTC

miguelrochefort wrote: post #13

komali2 wrote: post #12

Earlier quoted context omitted.

The debugger changed how I code. So much better than any other node debug solutions.

I'm confused. Did javascript people not use a debugger before VS Code?

It was console.log() all the way

Re: Visual Studio Code 1.8

#22

Post by ld00d » Wed, Dec 14, 2016, 9:57 PM UTC

miguelrochefort wrote: post #13

komali2 wrote: post #12

Earlier quoted context omitted.

The debugger changed how I code. So much better than any other node debug solutions.

I'm confused. Did javascript people not use a debugger before VS Code?

You can debug in Chrome (or any other browser). For node, you can run node-inspector which uses a browser for debugging.

Re: Visual Studio Code 1.8

#23

Post by azinman2 » Wed, Dec 14, 2016, 10:00 PM UTC

Loving the work done.. now we just need a more complete VIM mode implementation!

Re: Visual Studio Code 1.8

#24

Post by chronic92 » Wed, Dec 14, 2016, 10:05 PM UTC

hprotagonist wrote: post #14

Excellent. I have high hopes for a sublime-style "whole document" scroll bar in future releases.

You mean mini map?

Re: Visual Studio Code 1.8

#25

Post by itaysk » Wed, Dec 14, 2016, 10:06 PM UTC

Amazing pace and progress between each minor version

Re: Visual Studio Code 1.8

#26

Post by torgoguys » Wed, Dec 14, 2016, 10:06 PM UTC

Anybody know how many people are on the VSCode team? They're moving so fast in adding useful stuff with very few hiccups...I'm lovin' it.

Re: Visual Studio Code 1.8

#27

Post by kej » Wed, Dec 14, 2016, 10:06 PM UTC

hprotagonist wrote: post #14

Excellent. I have high hopes for a sublime-style "whole document" scroll bar in future releases.

It's in progress, see [0] this issue. Scroll to the bottom for an update from a few days ago.

[0] https://github.com/Microsoft/vscode/issues/4865

Re: Visual Studio Code 1.8

#28

Post by ggregoire » Wed, Dec 14, 2016, 10:08 PM UTC

torgoguys wrote: post #26

Anybody know how many people are on the VSCode team? They're moving so fast in adding useful stuff with very few hiccups...I'm lovin' it.

About 10.

From one member: "VSCode has a relatively small team compared to the size of the product" - https://github.com/Microsoft/vscode/issues/13138#issuecommen...

Re: Visual Studio Code 1.8

#29

Post by WA » Wed, Dec 14, 2016, 10:09 PM UTC

earthnail wrote: post #17

I know they're working on styling, but now that the titlebar is black, too (on Mac), I really, really would appreciate if the status bar would blend in, too.

Can't upvote this enough. One dev mentioned in a GitHub issue that the blue color is for branding reasons [1]. This is so absurd, it hurts. That status bar is the most distracting and annoying thing ever.

See link for suggestions how to mitigate. I use the tip from the person named sysrpl. VSCode is unusable with that blue color for me.

1: https://github.com/Microsoft/vscode/issues/1884

Re: Visual Studio Code 1.8

#30

Post by berdon » Wed, Dec 14, 2016, 10:09 PM UTC

_isus wrote: post #6

Finally, we get hot exit. :)

+1

Now I only hope they add in hot-disk support.

Sublime Text 3 checks to see if the currently opened version differs from the file system. If it does, it prompts the user to keep the current version or replace it with the disk version. VS Code just replaces the current version with the disk version and doesn't retain history so you can't undo this.

I lost about an hour of work yesterday because I had a file open in both VS Code and Sublime Text. Pressing save in Sublime Text wiped out all changes. :(