Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code 1.4

code.visualstudio.com

Post reply on HN
Print view View original

91–100 of 155 posts

Re: Visual Studio Code 1.4

#91

Post by flukus »

qarioz wrote: post #80
darren0 wrote: post #51

Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.

One day we will have a conversation about X text editor without mentioning vim. Not today.

That day will be long after all the non-modal heathens are converted.

Re: Visual Studio Code 1.4

#92

Post by erelde »

chenster wrote: post #44

I felt bad for Sublime. It would be hard for Sublime to compete with MS's free IDE. MS finally decides to take over the open source code editor market. VSC also borrowed many features from Sublime such as its famous integrated package manager and keyboard based shortcuts.

For me at least, it still lacks this 'perceived' reactiveness, that millisecond of delay that I don't have with Sublime or vim. I don't know if it's placebo but I have got to use what _feels_ right to me.

Re: Visual Studio Code 1.4

#94

Post by zvrba »

papaf wrote: post #90
zvrba wrote: post #78

I tried to use it for C++ development on Linux. A project I'm working on uses Qt, and I put QT's include directories into the configuration file as was described in documentation. I was unable to get autocompletion to work with Qt and after 10 minutes I gave up on it and went back to using Netbeans.

Have you tried Qt Creator? Its really good for normal C++ development and even better for Qt specific development.

A colleague uses it on OSX, and it's awful: unstable, crashes, hangs during debugging, the debugger doesn't always update the displayed values, doesn't grok auto declarations, etc. So far, Netbeans is the best free C++ IDE I've tried.

Re: Visual Studio Code 1.4

#95

Post by pjmlp »

chenster wrote: post #44

I felt bad for Sublime. It would be hard for Sublime to compete with MS's free IDE. MS finally decides to take over the open source code editor market. VSC also borrowed many features from Sublime such as its famous integrated package manager and keyboard based shortcuts.

This is why we cannot have nice desktop tooling unless it comes from Big Corp getting their revenue from licenses and what have you.

FOSS has spread so much that IT is probably the only industry where people nowadays expect to sell their work using tools they got from others for free.

It is very hard to make a living from donations and books (which tend to get pirated) alone.

Re: Visual Studio Code 1.4

#96

Post by z3t4 »

jordanlev wrote: post #17

Whenever I try a new text editor, I run into a problem: I absolutely love the feature where it auto-completes based on other words in open windows (or other files in the open project). But there's no official term for this so I can never tell if a text editor has it. Years ago this used to be called "hippie expand", but I can't figure out a more modern name that is used. Does anyone know what Visual Studio Code calls…

I've seen it called dumb auto-completion. Where intelligent auto-completion is called "intellisense".

intelligent auto-completion knows the variable type and available methods/properties. Whereas the dumb auto-completion just match the words.

Re: Visual Studio Code 1.4

#97

Post by keithnz »

berkeleynerd wrote: post #2

Great work on the integrated terminal. I'be been waiting for this. Might even fire up Windows 10 with Ubuntu shell and see how everything works together.

not well, big flaw with the ubuntu shell is that there is no reliable way to interact with the linux filesystem from a windows program ( like vscode ). You can work on the mounted C: drive /mnt/c . However, I have found a number of dev tools don't really like working with it ( meteor / mongo ). Thing crash. They work fine on the linux filesystem though, it's just you can't reliably use windows programs to access files, you have to use things like vim inside the shell to edit stuff.

Re: Visual Studio Code 1.4

#98

Post by arvinsim »

avolcano wrote: post #68
darren0 wrote: post #51

Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.

I wanted to use VSCode when I started writing TypeScript three months ago, but I found the Vim plugins super lacking, so I used Atom instead, which has a much more robust Vim plugin. However, I tried VSCode again last week after being disappointed by continued bugs in atom-typescript, and was happy to discover the Vim plugin ( https://github.com/VSCodeVim/Vim ) had made a ton of progress since I'd last given it a sho…

Is it as good as the Ideavim plugin for Jetbrains editors?

That is the benchmark that I use to judge other vim plugins.

Re: Visual Studio Code 1.4

#99

Post by flukus »

darren0 wrote: post #51

Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.

How does it handle other vim features like window splits, macros and programmability?

Re: Visual Studio Code 1.4

#100

Post by stinos »

avolcano wrote: post #68
darren0 wrote: post #51

Number one drawback of VSCode, for me, is poor vim keybindings, especially visual mode. If that was fixed I'd use it extensively.

I wanted to use VSCode when I started writing TypeScript three months ago, but I found the Vim plugins super lacking, so I used Atom instead, which has a much more robust Vim plugin. However, I tried VSCode again last week after being disappointed by continued bugs in atom-typescript, and was happy to discover the Vim plugin ( https://github.com/VSCodeVim/Vim ) had made a ton of progress since I'd last given it a sho…

I don't know what turned at MS exactly but something did, at least in the department where VS and VSC are developped. I've had major bad experiences with reporting bugs to MS in the past (almost as if they had a standard 'by design' or 'wontfix' message generator). The last couple of years however, not so much. Submit a report, get a reply like 'thanks for the detailed report, we're on it' and then the bug is fixed in the next service pack or version. And now they're also doing PRs for VSC and other things and the response times seem ok (well, a tleast yours was, but it's still sorta 'unseen' for MS). If it continues they might reach a point where the competition (including open source) starts to look very bad - there it's sometimes still the usual business as it was with MS: report a bug and/or PR, nothing happens, for months or even years.
Post reply on HN