Live data from Hacker News

Visual Studio Code 1.6

code.visualstudio.com

111–120 of 231 posts

Re: Visual Studio Code 1.6

#111
post #109
post #108

I don't know, every time I see a new release of Atom or VS code and people praising it in comments I go ahead and download it and open the project that I am currently working on in Sublime for side by side comparison. And what strikes me most is how smooth Sublime is compared to Visual Studio Code or Atom (at least on my mac, I dont know about windows experience). Scrolling is much slower in VSC and searching through…

Here's a good test: Do you want a text editor, or do you want something that's close to an IDE? Atom/VS Code exist to be IDE-y, not as thought experiments on text editors in the browser. Their advantages are in the ease of developing extensions and tools that aren't part of the core package. The difference is similar to Vim/Emacs. Of course Vim has some IDE-y plugins, but they're rarely as rich as what ends up gettin…

Choppy scrolling is a high price to pay for an IDE in my opinion.

Re: Visual Studio Code 1.6

#112
post #18

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.

You should submit an issue with a repro: https://github.com/microsoft/vscode-go Go plugin is very much actively maintained.

Good point. I had been meaning to do that for a while. Thanks for the nudge: https://github.com/Microsoft/vscode-go/issues/521

Re: Visual Studio Code 1.6

#113
post #47

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 have little experience with both, but the developers of LLDB have a goal of making more informative error messages. This was successful enough that GDB devs were compelled to mimic this behavior, making their error reporting more accessible. As far as I know, LLDB still has the advantage in this regard.

Re: Visual Studio Code 1.6

#114
post #42

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...)

I've not tried LiteIDE since it first came out. I did not enjoy the experience at the time. The toolchain in VSCode is really nice. You can run tests from your cursor, the file, or the package. There is a built in terminal if you want it. Jump and peek definition for stdlib and imported packages. GoImports works, but so does a cmd+p prompt where you can ">Go: Add Import" and specifically add the import you want so autocomplete just starts working for it. The linting catches me all the time when I type fmt.Println instead of fmt.Printf or have the wrong format types in the string. You have to mouse over something to get its method signature or type, but I've gotten used to it. I even have found myself using its git diff viewer. It also has delve debugger integration, but I've not had the chance to use it yet.

I also use VSCode for bash, python, perl, HTML, markdown, and probably a few others that I'm forgetting. However, I primarily use it for Go.

Re: Visual Studio Code 1.6

#115
post #98

Now MS just have to seamless integrate their Ubuntu Bash filesystem with the Windows filesystem so I can create files in VSCode and access then in the ubuntu shell. They will build the best dev environment.

An environment that doesn't match your production server is far from being the best one (this doesn't apply to all cases but you get the idea)

Agree 100%. Ubuntu desktop and server is gaining market share among devs (those who prefer working on bare-metal) for precisely this reason.

Re: Visual Studio Code 1.6

#117
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.

Try this https://code.visualstudio.com/docs/editor/editingevolved#_co...

and for multi cursor https://code.visualstudio.com/docs/editor/editingevolved#_mu...

Sean - a member of the @code team.

Re: Visual Studio Code 1.6

#118
post #110
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…

"As much as I wouldn't have believed this 10 years ago, Microsoft does open source better than almost everyone." This. They are treating vscode like its a core (cash cow) product. I'd say google embraced/adopted open source early on and now microsoft is playing catchup while now becoming one of the very best to do it.

I see Microsoft's open source efforts as a means to an end.

Re: Visual Studio Code 1.6

#119
post #97
post #53

Earlier quoted context omitted.

Hi! I'm one of the core developers of VSCodeVim. Shift-Y and Shift-P absolutely work for me, so please report on our issues page if they continue to not work for you: https://github.com/VSCodeVim/Vim/issues I would also be really interested to hear about the other holes that you're running into. Always trying to make a better Vim experience for you :)

I just wanted to say thanks. A Vim with intellisense that I can step through with the debugger. I've been waiting 15 years for this.

jaredpar's VsVim will give you that in Visual Studio.

Re: Visual Studio Code 1.6

#120
post #74
post #70

Earlier quoted context omitted.

For me it's also amazingly good for C and Go development.

oh that's actually really good to hear - my team has a lot of backend services in Perl (yeah..) that we're moving to Go :)

Why would you rewrite already-working services written in an expressive and battle-tested language to a fad 1970s-style language?

It's like being in the late 90s and replacing your existing infrastructure with Java hype, except with a language somehow worse but justified with Rob Pike's pseudointellectual bullshit.

Post reply on HN