Live data from Hacker News

Visual Studio Code 1.9

code.visualstudio.com

251–260 of 312 posts

Re: Visual Studio Code 1.9

#251

Anyone know if the C# plugin supports cshtml files yet? The lack of autocomplete, inspections and so on really hampers web development with it. I've now switched entirely to using Rider because of this. While it's still early days for Rider (and it makes my Laptop's fans spin nonstop), being able to hastily edit my views makes it more than worth it. (And integrated ReSharper is always good!)

If you are using C#, why not use Visual Studio?

Re: Visual Studio Code 1.9

#252
post #19

Another great release! Maybe I'm just squarely within the target audience of VSCode, but I'm consistently impressed by how many of my pain points just magically go away with each new iteration.

I come from WebStorm, Sublime and Atom. Atom and WebStorm felt rather clunky. Sublime was super fast, but somehow lacked behind in new features. VSCode is a revelation for me :)

whenever I try Webstorm, my laptop starts sounding like an Airbus A380. What makes VSCode different from Atom though is, VScode uses Monaco which is significantly better and also the start up is faster with VSCode.

Re: Visual Studio Code 1.9

#253

Earlier quoted context omitted.

It's the only practical way to do cross-platform .NET Core development.

If that's true, then I'd recommend not using either .NET or VSCode if cross platform matters to you. Historically speaking, Microsoft will break compatibility when it suits them.

I think you confuse Microsoft with Apple.

Re: Visual Studio Code 1.9

#254
post #216

Earlier quoted context omitted.

I'm a .net developer, I still install cygwin/bash on my computer because I can write stuff quicker and better. PS get's incredibly verbose for anything non trivial. I learned powershell long before bash too.

Calling Powershell incredibly verbose is about the same as calling C# incredibly verbose. Sure, perhaps they're not as compact as some of the incredibly information-dense perl scripts that people come up with. I'd wager though that it's easier to understand what a random powershell script is doing than a random perl or bash script that pipes output throgh a dozen utilities.

I've got an example of powershell getting verbose here: http://flukus.github.io/2015/03/13/2015_03_13_Powershell-is-... . Ignore the rest and look at the example where I'm trying to copy a directory recursively and with a filter. In bash the same task is a relatively simple one liner:

  find . -type f -name '*.html' -exec cp {} /home/new_dir/{} \;
If you know a simpler way in powershell please post it though.

Re: Visual Studio Code 1.9

#255

I am surprised at the amount of semi-negative comments here. Yes, some features are yet to be implemented, (it's still a fairly young project and you can always follow GitHub issues on progress), but for an Electron app, it's surprisingly fast and capable. The Microsoft-developed Go plugin makes it the best Go IDE out there, the devs, (Ramya Rao etc.) are super responsive and really trying to resolve issues quickly.…

> makes it the best Go IDE out there

I will respectfully disagree and say that gogland (while still in a pre-release state) is much much better.

Re: Visual Studio Code 1.9

#256
I work on Chromium and I test every VS Code version to see how it performs with the Chromium source code (except third_party). This is the first time I'm impressed. My observations:

1. Go to file is a little bit slower than Sublime Text but the extra features in VS Code make that tradeoff worthwhile. 2. The C/C++ extension enables go to definition/header without any extra configuration. 3. I like that it runs on top of Electron which is after all a fork of Chromium. 4. I haven't tried the debugger yet but I'm hopeful that will work fine too.

I'll keep playing around with it and maybe even switch from Sublime Text.

Re: Visual Studio Code 1.9

#257
post #216

Earlier quoted context omitted.

I'm a .net developer, I still install cygwin/bash on my computer because I can write stuff quicker and better. PS get's incredibly verbose for anything non trivial. I learned powershell long before bash too.

Calling Powershell incredibly verbose is about the same as calling C# incredibly verbose. Sure, perhaps they're not as compact as some of the incredibly information-dense perl scripts that people come up with. I'd wager though that it's easier to understand what a random powershell script is doing than a random perl or bash script that pipes output throgh a dozen utilities.

Perl scripts can be vastly more powerful than PS. Perl is a full blown general purpose programming language with a massive collection of libs and frameworks.

It is however very powerful that Perl can be used in bash pipelines. But that is also true for any Unix tool that takes I/O.

So Bash is also very powerful with the help from all its friends that can be used with pipes. Shell native.

And you don't HAVE to code Bash in the most convoluted way possible. Sane code structure and naming goes a long way.

Re: Visual Studio Code 1.9

#259

Earlier quoted context omitted.

It's the only practical way to do cross-platform .NET Core development.

If that's true, then I'd recommend not using either .NET or VSCode if cross platform matters to you. Historically speaking, Microsoft will break compatibility when it suits them.

The project is Open Source, MIT licensed. If they break compatibility you (or someone else) can just fix it. No difference from any other OpenSource editor.

Re: Visual Studio Code 1.9

#260
post #218

Earlier quoted context omitted.

If you mostly just want the memorized shortcuts to work, they tend to work OK in VSCode, Atom, IntelliJ and even Emacs - Spacemacs is even a better ViM for some.

As someone who did a fair amount of hacking in vimL, evil-mode is a drastically improved vim. It gets basically everything right, out of the box, and extending it isnt nearly as painful as using vimL or interacting with vim's Python API.

It doesn't, in my experience, get insert mode shortcuts like C-h right out of the box because it clashes with emacs' help mode functionality.
Post reply on HN