Live data from Hacker News

Visual Studio Code 1.0

code.visualstudio.com

421–430 of 487 posts

Re: Visual Studio Code 1.0

#421
Today I used VSCode to write a slack bot in NodeJS.

The editor experience was smooth and fast, with fast intellisense.

I had NodeJS debugging working after 5 minutes reading a VSCode NodeJS page on the VSCode site and clicking a couple of buttons in the editor.

I had a very good initial experience and will use again.

Re: Visual Studio Code 1.0

#422
For some reason I can't stand the fact that VS Code drops .vscode files all over my directories. I feel like I'm working with CVS again. I haven't played with it much and not at all lately, but the last time I tried editing anything in VS Code it generated these hidden files all over the place and drop me up a wall. That may be configurable and it may have changed with 1.0, I'm not sure.

It's also, just very slightly, too slow. By too slow I mean that everything I do just lags a tiny bit; I can type characters faster than it can put them on the screen, clicking in the file browser is not instantaneous, etc. It's a small thing but it really bugs me. I guess I'm just spoiled by ST3. :/

Re: Visual Studio Code 1.0

#423
post #276

I tried VSCode for the last couple of months and it didn't sell me. It's noticeably slower than Sublime on a good workstation and it has a bunch of very minor annoyances that Sublime simply doesn't have. When you encounter these annoyances dozens of times a day, it really turns you off from using it because a good editor should make you happy, not infuriate you. For example, the way VSCode deals with multiple buffers…

I feel the same way. I tried to like VSCode but it's just all the small things that trip me up. I've really come to depend on STs mini-map and miss it when it's not there. VSCode is just slightly slower than I feel it should be, causing me to pause and crash my train of thought.

Re: Visual Studio Code 1.0

#424

Earlier quoted context omitted.

Seriously try gvim. Not vim where you need a long ass cheat sheet just to create a new tab or move between splits. But gvim where you can be productive and use the mouse and menus when necessary.

The one thing that kills gvim for me is the inability to have one session with multiple windows. I use it anyway.

Try Emacs with vim bindings and you'll have it, its GUI is a client that connects to a server

Re: Visual Studio Code 1.0

#425
post #124

Earlier quoted context omitted.

For example the Git integration is awesome and even better than Atom's (you can commit, push, ...). Of course you can do a lot with extensions, but at least in Atom's case they break a lot for me.

Well, okay, let's talk about that. Is having source control in your text editor enough of a benefit to one's daily routine as to be a step change of productivity or quality of life? It may be for you and I'm not saying you're wrong for that, I'm asking because it isn't for me; I have an alt and a tab key. Bear in mind that the claim wasn't that it's better in some ways , but that it's sweepingly better than the stuff…

For me it does, depending on the project. (Using emacs/magit, having a dedicated buffer just for magit.)

I want to keep on top of my current branch, what is untracked, what is unstaged and staged, quick diffing, etc. It actually helps a lot with productivity since I don't have to actively query for this information when it's all in one screen.

If I used another editor, I would like to have similar features. Maybe it can be done, but I am quite fluent in magit already, and one major thing keeping me from moving to another text editor for my current projects (if it actually mattered.)

Re: Visual Studio Code 1.0

#426
post #419

Earlier quoted context omitted.

I'm the maintainer of amVim. I don't know if you tried amVim. It supports Visual and VisualLine. Also, you may find it handles detail behaviors of Vim much better.

Fantastic, that's a lot better than the other Vim plugin I tried! Thank you. g; and W/E support would be nice (as someone said on this thread, everyone has a different subset of Vim they use ;-) )

Thanks! Cloud you open an issue on Github repo here: https://github.com/aioutecism/amVim-for-VSCode

Re: Visual Studio Code 1.0

#427
I find Visual Studio Code much better with plugins than Atom. Atom died after installing the Nuclide plugin suite and would not work until I uninstalled those plugins. Code on the other hand runs plugins in a separate thread meaning it does not tend to dies so easily. VS Code rocks!

Re: Visual Studio Code 1.0

#428

Earlier quoted context omitted.

I'm the maintainer of amVim. I don't know if you tried amVim. It supports Visual and VisualLine. Also, you may find it handles detail behaviors of Vim much better.

It looks like a big improvement, but I notice visual mode doesn't work with cursor keys, and I'm also not seeing an ex-mode (eg. :w). Would love to see these implemented :)

Thanks! Cursor keys support in Visual mode will just be a few lines of code to implement. Cloud you open an issue so we can track them easily? https://github.com/aioutecism/amVim-for-VSCode

Oh. ex-mode is not something I'm planing to implement. They are often a lot easier to do with Cmd+Shift+P.

Re: Visual Studio Code 1.0

#429

Earlier quoted context omitted.

Just wanted to say I find Notepad++ to be an excellent tabbed editor, especially for XML or SQL. I use it on windows all the time and really miss it on OS X where I find Textmate to be a bit awkward.

I've been a long-time fan of Notepad++, but it's a text editor. You can extend it to make it work better with specific programming languages (e.g. here's a post I wrote 10 years ago about adding language support http://weblogs.asp.net/jongalloway/creating-a-user-defined-l... ) but it's fundamentally a text editor. VS Code is a code editor. It has IntelliSense (not text-matched autocomplete, IntelliSense), debugging s…

As you say, both are useful for different things. They complement each other if you use the right tool for the right job.

I find Notepad++ is great for handling really large files and changing UTF encoding or line endings. VS is good for pretty print formatting code/XML to be more readable, among many other non-text things such as debugging.

Re: Visual Studio Code 1.0

#430

Earlier quoted context omitted.

VSCode doesn't even change the way code was written on Mac or Windows. Let me turn the question around. What does VSCode do that Sublime, Atom, Emacs and Vim doesn't? Nothing. That is not to say that VSCode is bad. It's a decent editor. But the only reason I found Atom and VSCode to be interesting at all, was that way more people know Javascript than ELisp or VimScript, and so I figuere that the quality and quantity…

>VSCode doesn't even change the way code was written on Mac or Windows. That's probably because those two platforms have already had superior tools for a long time. On Linux, vim reigns supreme. So it is easier to revolutionize code editing on Linux

All three platforms have had access to Vim, Emacs, LightTable and Sublime. VSCode brings nothing new to the table other than Javascript as a plugin-language.

The fact that you think that VSCode is revolutionary compared to vim, only displays your ignorance. Vim can do the exact same things VSCode can, and it has been able to do so for quite a bit longer.

Post reply on HN