Live data from Hacker News

Visual Studio Code 1.7

code.visualstudio.com

121–130 of 180 posts

Re: Visual Studio Code 1.7

#121

When MS gets into something, they really get into it. VS Code has exceeded pretty much all my expectations with the pace it has been progressing at.

Microsoft really knows how to do dev tools. If only they were as disciplined and effective with some of their other product lines.

Re: Visual Studio Code 1.7

#122
post #51

Earlier quoted context omitted.

what would something 10x better than vim/emacs/vscode look like ?

Gary Bernhardt's "A Whole New World" had a cool vision for what the future of editors might look like: https://www.destroyallsoftware.com/talks/a-whole-new-world

And here's[1] a project inspired by Gary's talk to design and implement a new escape protocol and a new virtual terminal to support these sorts of use-cases. (I'm not involved with the project.)

[1] https://github.com/withoutboats/notty

Re: Visual Studio Code 1.7

#123

They had to rollback the update: > Unfortunately, we needed to roll back the 1.7 release of VS Code. One of the great new features in 1.7 is the automatic acquisition of typing files when writing JavaScript and TypeScript. These typings files drive the IntelliSense (code completions) experience in the tool. The feature was so great that we started to overload the npmjs.org service. The right thing to do in the short…

It was funny, I've just installed vscode in an old machine and came to HN. On the first page there as a newer version. Holy Shit! They've updated between the install and visiting the page. I was almost buying Microsft

Re: Visual Studio Code 1.7

#124

Dear Microsoft, PLEASE native SFTP sync support. I will switch from Sublime permanently.

I've found the ftp-sync extension's sftp support adequate for my use so far. I've definitely found full-syncs to be a bit slow when there's a lot of stuff in the folder, but it seems ok so far.

Re: Visual Studio Code 1.7

#125
I couldn't find a good tutorial about using VSCode for Python development. I'd like to setup debugging, intellisense and the interactive shell, but the info is sparse. Do you have any suggestion?

Re: Visual Studio Code 1.7

#126
post #33

Ah haha this is too funny, I just this morning caved from trying to have a functioning version of Ubuntu on the macbook work gave me, booted back into OSX, and spent a good 30 minutes scrolling through the VSCode keyboard shortcuts JSON, writing down the ones I was interested in relearning on post-its and lining them around my monitor. And not four hours later they release a pretty little printable PDF. Not very on t…

It's not like it was very difficult to have a simple key binding list before the update. There are many json to html table websites out there, or you could just paste it in vs code and use multiple cursors to remove all the json syntax in like 10 seconds.

Re: Visual Studio Code 1.7

#127

They had to rollback the update: > Unfortunately, we needed to roll back the 1.7 release of VS Code. One of the great new features in 1.7 is the automatic acquisition of typing files when writing JavaScript and TypeScript. These typings files drive the IntelliSense (code completions) experience in the tool. The feature was so great that we started to overload the npmjs.org service. The right thing to do in the short…

I was so confused. Thank you.

Re: Visual Studio Code 1.7

#128

I love using VIM to edit, but stuff like the following makes it hard for me to resist switching. "ATA makes typings files almost invisible. A TypeScript language server that has ATA enabled watches your package.json files and automatically installs the typings files of all dependencies in a cache on your file system. It does the same when it finds references to well known client-side libraries. When you then invoke I…

There's no need to switch editors for that. The language servers can be used by any editor that supports the language server protocol. As far as I know nobody has written a plugin for Vim yet, but here's a discussion issue on the neovim tracker: https://github.com/neovim/neovim/issues/5522

Try Tsuquyomi: https://github.com/Quramy/tsuquyomi It works.

Re: Visual Studio Code 1.7

#129
post #54
post #40

Earlier quoted context omitted.

The biggest thing for me has been the consistency. They already had an amazing IDE (Visual Studio), then they buckled down and made an amazing paired-down version (VSCode). It works well, does all the things I'd want and then some. Compare to Google releasing a chat client / message handler (google voice app), another one (hangouts), taking away functionality (removing shared sms/hangouts convos), then releasing two…

What about the Surface Book?

Regarding Linux... the Surface Book (and Pro) are rather unique devices, as far as hardware is concerned. You loose a lot of core functionality if you run anything except Windows on them. I've tried.

If you want a strictly Windows-only device, they're not bad. (Buggy drivers aside.) The N-trig stylus technology is absolutely amazing if you do graphic design. But if you want to dual boot into Linux, you'll be happier with a more traditional laptop.

To be honest, I tried both a Surface Pro 3 and a Surface Book as my primary laptop. In the end, I keep going back to my 2012 MacBook Air. At least for me, Apple still has an edge in overall experience.

Re: Visual Studio Code 1.7

#130
post #106
post #104

Mostly ruby developer here these days. Just installed VSCode, installed a Ruby plugin (with the required ruby-debug-ide prereq), and opened a project. Debugger seems to just work. Very impressive. Tried the vim bindings, doesn't seem to be working so well. This is something I'm used to -- vim bindings rarely work well outside of Vim. Basics like "diw" (delete inside word) don't work though. I'll probably stick with V…

Which extension are you using? I'm using vscodevim and diw, ciw, and the likes work.

Was using vimStyle, I'll try some of the other ones.
Post reply on HN