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

Visual Studio Code 1.6

code.visualstudio.com

Post reply on HN
Print view View original

41–50 of 231 posts

Re: Visual Studio Code 1.6

#41

Post by LyalinDotCom »

NicoJuicy wrote: post #11

I always had Visual Studio for .Net development and for everything else it changed. First Notepad++, then Brackets, Atom, then Sublime Text and since 4 months it's always been Visual Studio Code. It's nuts how fast Visual Studio Code is evolving. Good job Microsoft, developers and the community. My only fear is that the application would become bloated, but for now it's still blazing fast. Even when i have to much ex…

We're very committed to fight bloat, as with any large software project its always a risk so please help keep us honest

Re: Visual Studio Code 1.6

#42

Post by mappu »

sethammons wrote: post #16

I switched from _years_ on sublime (paid) to vscode in a hot minute for Go development. Awesome jump to declaration and linting. There is one thing it has trouble with and that is auto-complete from within sub-packages. Not sure why yet.

I'm on LiteIDE for Go - have you tried it? If so, do you know how VS Code compares to it?

I have a very multilingual project so i'm resigned to using multiple IDEs anyway (LiteIDE for Go, VS for C#, Qt Creator for C++/Qt, Eclipse PDT for PHP, Notepad++ for bash...)

Re: Visual Studio Code 1.6

#43

Post by donatj »

I love VSCode. Sublime still trumps it in two places though - multi-cursor support in VSCode isn't quite as powerful as Sublime I particularly miss the middle click, drag, select rectangle [1].

The other area is that global search/replace isn't as powerful or nearly as quick.

I'm hoping both of these are things they fix in time.

[1] http://jdon.at/19OUp

Re: Visual Studio Code 1.6

#44

Post by JoelBennett »

daeken wrote: post #24

I've recently switched to VS Code full time for C# and Python development and I couldn't be happier. While I miss some of the more intelligent intellisense from full VS, I love that I can do all of my dev on OS X. Its integration with .NET Core makes my life easy; really can't complain at all.

I was curious to know how it worked for Python. I might have to give it a serious go...

Re: Visual Studio Code 1.6

#45

Post by shogun21 »

donatj wrote: post #43

I love VSCode. Sublime still trumps it in two places though - multi-cursor support in VSCode isn't quite as powerful as Sublime I particularly miss the middle click, drag, select rectangle [1]. The other area is that global search/replace isn't as powerful or nearly as quick. I'm hoping both of these are things they fix in time. [1] http://jdon.at/19OUp

Middle-click and drag is a game-changer! Thanks for the heads up.

Re: Visual Studio Code 1.6

#47

Post by Cyph0n »

steveklabnik wrote: post #37
Cyph0n wrote: post #36

Earlier quoted context omitted.

Damn, seriously? I'm going to be writing some C++ soon, and I'm also planning to learn gdb, so I guess VS Code it is then. Thanks for the heads up!

There's also a brand-new lldb plugin too https://marketplace.visualstudio.com/items?itemName=vadimcn....

Which would you recommend I start with as a newcomer to the low-level debugging world - gdb or lldb? I have some experience debugging assembly in x86 real mode (yep, my class was outdated!).

Re: Visual Studio Code 1.6

#48

Post by mafuyu »

david-given wrote: post #20
tomdale wrote: post #3

I have been using VS Code as my full-time editor for a few months now and couldn't be happier. Originally I was only using it for TypeScript projects, where the language integration is top-notch, but eventually found myself using it all the time. I use the vim plugin, which is surprisingly good although it does have a few issues still. The best thing about VS Code (and Microsoft's other big open source project, TypeS…

I'm currently switching from gvim to vscode and back again every five minutes, in order to use vscode's debugger --- it's gdb integration is the best I've seen bar none [1][2]. If the vim emulation was good enough, I'd switch in a moment. Which, unfortunately, it's not, for me: the biggest omission is shift-Y/shift-P for yank and paste, which I use constantly, but there's holes everywhere. (Also, the way the vscode's…

Just installed VS Code with the Vim extension and everything seems to be working pretty well for me, including yy and shift-P. I had to set "vim.useCtrlKeys": true to enable some of the keybinds that override VS Code bindings.

Re: Visual Studio Code 1.6

#49

Post by steveklabnik »

Cyph0n wrote: post #47
steveklabnik wrote: post #37

Earlier quoted context omitted.

There's also a brand-new lldb plugin too https://marketplace.visualstudio.com/items?itemName=vadimcn....

Which would you recommend I start with as a newcomer to the low-level debugging world - gdb or lldb? I have some experience debugging assembly in x86 real mode (yep, my class was outdated!).

I personally don't have enough direct experience with lldb to say. I've heard good things. It's on my list of stuff to try out.

Re: Visual Studio Code 1.6

#50

Post by steveklabnik »

mafuyu wrote: post #48
david-given wrote: post #20

Earlier quoted context omitted.

I'm currently switching from gvim to vscode and back again every five minutes, in order to use vscode's debugger --- it's gdb integration is the best I've seen bar none [1][2]. If the vim emulation was good enough, I'd switch in a moment. Which, unfortunately, it's not, for me: the biggest omission is shift-Y/shift-P for yank and paste, which I use constantly, but there's holes everywhere. (Also, the way the vscode's…

Just installed VS Code with the Vim extension and everything seems to be working pretty well for me, including yy and shift-P. I had to set "vim.useCtrlKeys": true to enable some of the keybinds that override VS Code bindings.

Yeah that's a good setting.

The parent is correct though, Y doesn't work. I thought it did, so I opened it up to check, and turns out that I didn't realize this because I tend to do Vy instead of Y.

Post reply on HN