Visual Studio Code 1.6 • Hacker News Board

Re: Visual Studio Code 1.6

#131

Post by badlogic » Tue, Oct 11, 2016, 7:06 AM UTC

pYQAJ6Zm wrote: post #113

Cyph0n wrote: post #47

Earlier quoted context omitted.

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.

You must be confusing LLDB/GDB with Clang/GCC. LLDB and GDB are debuggers, they generally do not produce many error messages. Clang has/had better error messages than GCC.

Re: Visual Studio Code 1.6

#132

Post by Matthias247 » Tue, Oct 11, 2016, 7:14 AM UTC

neves wrote: 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.

What are you missing specifically there? The windows filesystem is already mounted in bash for windows, so you can access files created from Code there.

However I didn't found that of too much use since I can't run windows executables from there and so WSL is pretty isolated. Instead I still use msys/cygwin for the shell which has it's quirks (file path magic) but works. In combination with docker for windows and volume mounts there I can even cross compile Linux executables on the windows shell, which is pretty cool.

Re: Visual Studio Code 1.6

#133

Post by skoczymroczny » Tue, Oct 11, 2016, 7:15 AM UTC

taneq wrote: post #123

happy-go-lucky wrote: post #118

Earlier quoted context omitted.

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

Name one entity whose open source efforts are not a means to an end. Even OSS nuts like Stallman have their motivations (in his case, furthering his ideology). That doesn't invalidate their contributions.

Stallman is FOSS, not OSS.

Re: Visual Studio Code 1.6

#134

Post by baq » Tue, Oct 11, 2016, 7:35 AM UTC

PeCaN wrote: post #120

elnado wrote: post #74

Earlier quoted context omitted.

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.

depending on technical debt in Perl code (which is quite easy to incur) it might make sense if you're still making changes to the project. also single-binary deployment is always nice, though in the world where docker exists not as big of a deal as it used to be a few years ago.

Re: Visual Studio Code 1.6

#135

Post by thomasahle » Tue, Oct 11, 2016, 7:37 AM UTC

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…

What do shift+Y and shift+P do? Are they the same as y and p, but in insert mode?

Re: Visual Studio Code 1.6

#136

Post by suprfnk » Tue, Oct 11, 2016, 7:51 AM UTC

thomasahle wrote: post #135

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…

What do shift+Y and shift+P do? Are they the same as y and p, but in insert mode?

In insert mode? How would you type uppercase X and P then?

Re: Visual Studio Code 1.6

#137

Post by matthewking » Tue, Oct 11, 2016, 8:03 AM UTC

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.

Seconded, I've been writing c# with asp.net core solely on OSX for a few weeks now, I've not run into a single thing that I miss from full Visual Studio yet, living the dream!

Re: Visual Studio Code 1.6

#138

Post by renke1 » Tue, Oct 11, 2016, 8:06 AM UTC

Stratoscope wrote: post #51

renke1 wrote: post #26

I switched from Atom to Visual Studio Code for my new project (TypeScript frontend and Go backend) and I am really impressed. Although the Go support is really good in Atom (missing a few things like debugging and jump to definition via mouse), the TypeScript support is significantly slower than in Visual Studio Code. There are few things missing Visual Studio Code though: Multiple top-level folders, customizable UI…

You can customize the font face and font size. It even supports proportional fonts! You just have to hand-edit settings.json to do it. Go into File/Preferences/User Settings and copy the editor.fontFamily and editor.fontSize lines from the left panel to the right and edit them to what you want. What bothers me about the font rendering, though, is that for some reason they have disabled ClearType! Everything uses gray…

Yes, the editor font can be changed. The interface font (menus, sidebars) not so much. The only thing you can do is scale the whole UI which feels awkward at best.

Re: Visual Studio Code 1.6

#139

Post by wingerlang » Tue, Oct 11, 2016, 8:15 AM UTC

Achshar wrote: post #8

What I find to be hilariously missing is drag & drop for the selected text. I tried switching to VS code a couple of days ago and realized I couldn't do such a basic thing. That and a decent FTP extension. No one wants to sync their entire project just to upload a single file. ugh.

I see lots of the responses are surprised people actually use drag'n drop for text. I just want to chime in that I use it a lot, although I can't really give any concrete scenario when I do it. Sometimes it just makes sense.

Re: Visual Studio Code 1.6

#140

Post by HNSucksAss » Tue, Oct 11, 2016, 8:17 AM UTC

"We added a new command to let you quickly move between open Windows of VS Code. Simply open the Command Palette (⇧⌘P) and type Switch Window. A dropdown will appear showing all the opened VS Code Windows..."

That doesn't seem fast.