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

121–130 of 155 posts

Re: Visual Studio Code 1.4

#121

Post by yAnonymous »

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.

Don't feel bad for them. They paved the way for all the great text editors we have now, but they missed the point where they should have opened up their core. If they didn't, there's a good chance Atom, VSC and others wouldn't exist.

Re: Visual Studio Code 1.4

#123

Post by killercup »

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 too wrote a PR a few days ago to not switch to visual mode when selecting text in insert mode (which breaks snippets and wrapping text in braces).

I'm pretty busy right now, though, and will probably not get to finish it in the next week. If anyone wants to pick it up, I'd be really happy: https://github.com/VSCodeVim/Vim/pull/544

Re: Visual Studio Code 1.4

#126

Post by StevePerkins »

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.

I don't see a problem with this. Frankly, there are probably more people using Vim keybindings in another text editor than using raw Vim itself.

Re: Visual Studio Code 1.4

#127

Post by StevePerkins »

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.

The plugin that comes closest is "VimStyle", which ironically has the lowest number of installs and ratings out of the top three. I assume that's because it was a bit later to market. However, the top two are garbage.

Re: Visual Studio Code 1.4

#128

Post by Mao_Zedang »

asimuvPR wrote: post #81
sho_hn wrote: post #60

Earlier quoted context omitted.

I'm curious, what's the thought behind having an official company-wide text editor? The companies I've worked for usually take the route of "leave their choice in tools up to them", which I appreciate.

We needed a good standard setup that fit our needs. People can opt to use something else as long as their code meets the style guidelines. But its easier to use the same tool. We share tips and tricks a lot. That way we improve our workflow as a whole. Why not vim itself? We tried it. They are more used to GUI centric editors. (shrugs)

While I agree with what you are saying, editor config is a good tool to enforce coding standards across multiple editors (as a bonus it already supports VS Code)

http://editorconfig.org/

Re: Visual Studio Code 1.4

#129

Post by coldtea »

modarts wrote: post #69
asimuvPR wrote: post #43

Earlier quoted context omitted.

Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.

What's the rationale behind forcing people to use an editor (especially a specific editor for a single language)?

To get stubborn people to try new tools for a change.

Of course their goal is conformity, easier management (e.g. everybody gets the same linters, code formatters, etc), but the above is a nice side benefit too.

There are tons of people using some antiquated editor and swearing by it, that get amazed when they are forced (by a job) to use a modern IDE and see what it can do for them.

And I'm not talking about Emacs etc -- which can do a lot if you set it up right, I talk about people coding e.g. Java with Slickedit or whatever. Heck even Vim users are sometimes surprised of the convenience (and turn-key use) of embedded debugger, build system, actual AST-based auto-completion, refactoring tools, etc.

Because when we code, actually editing text is the least of our worries, and yet this is what most simple "programming editors" focus on -- it's not like we're building huge ASCII art paintings...

Re: Visual Studio Code 1.4

#130

Post by IshKebab »

was_boring wrote: post #76
jhofker wrote: post #72

Earlier quoted context omitted.

What are some of the custom tasks you've been using in it? I've found I'm using the integrated terminal significantly more than I ever did with the tasks, but maybe I'm missing something really cool.

I work across many code bases and technology stacks so I use it to standardize tasks such as: build, test, continuous testing, running and linting. Without it I would have to remember the command for each code base.

How is that different to normal IDEs?
Post reply on HN