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

Visual Studio Code 1.9

code.visualstudio.com

Post reply on HN
Print view View original

181–190 of 312 posts

Re: Visual Studio Code 1.9

#181

Post by rubber_duck »

yokohummer7 wrote: post #38

This is an off topic, but I just learned from the article that PowerShell will soon be the default in place of cmd.exe in Windows 10. I welcome this change as I found the experience of using PS was superior to that of bash/zsh in general cases. But I hope they figured out the performance problem. As of writing, in the stable version of Windows 10, PS is perceptually slower than cmd, so I was forced to use PS only whe…

On that note if you are a .NET developer you owe yourself to learn PS and how to write cmdlets, it's such a powerful and easy way to expose a CLI for your .NET app compared to stdio and command line arguments parsing - it's incredibly powerful and trivial to do.

Unfortunately most .NET devs are programmers who grew up with VB, RAD and GUI tools they don't understand the value of exposing UNIX like small functionality CLI commands over big monolithic services, GUI apps, etc.

Re: Visual Studio Code 1.9

#182

Post by AsyncAwait »

titanix2 wrote: post #76
joekrill wrote: post #51

I keep trying VSCode, but the main thing that keeps me going back to Atom is the fact that I have to do everything at the command line or by editing an enormous json file. Maybe I'm spoiled, but I'd much rather have a nice UI to deal with settings than have to figure out that, say, in order to show line numbers I have to modify "editor.lineNumbers" and set it to "on" (or is it "true"? or 1? I can't remember... let me…

I share your opinion on the settings and command line. While I like it to loads faster than full fledged Visual Studio, in a year or so of using it on Mac OS I still doesn't use even 1% of its features because they are not _discoverable_ at all. Modifying or doing anything beyond text editing require googling. The same apply for using langages extensions beyond syntax coloring. Even Intellisense does not works as exp…

> still doesn't use even 1% of its features because they are not _discoverable_ at all.

There are now categories in the settings file, a search bar and auto-completion, which should make discovery easier.

> The same apply for using langages extensions beyond syntax coloring.

Do you mean to say that extensions at https://marketplace.visualstudio.com/VSCode are hard for you to discover or that too much of your required functionality is in extensions?

> Even Intellisense does not works as expected out of the box so I don't use it.

If you have found a bug, it would be great to report it at https://github.com/Microsoft/vscode/issues

Re: Visual Studio Code 1.9

#183

Post by greggyb »

alkonaut wrote: post #132
sljkdjaldjo wrote: post #96

Earlier quoted context omitted.

well, it's an editor for programming. those tools are usually all about typing text, automatically completing text, and validating text. appling those idea to a json config file shouldn't be allien to a programmer.

I use fancy autocompleting and validating text editor for exactly that reason - remembering if it's "on" or "true" or "yes" is too much overhead. So yeah, json or (preferably) any other markup for settings is fine so long as it hints me with possible values as I type, tooltips each variable with its meaning and so on.

> so long as it hints me with possible values as I type, tooltips each variable with its meaning and so on.

VSCode does this and more. See sibling comments.

Re: Visual Studio Code 1.9

#184

Post by testUser69 »

AsyncAwait wrote: post #41

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

All editors support go really well, that's because go has official tools that integrate with editors (guru, for example).

At the top of the read me is the feature list for the vscode-go:

https://github.com/Microsoft/vscode-go

This is the feature list for vim-go:

https://github.com/fatih/vim-go

looks a little longer, but if you notice they both use the same back end tools. I see that VSC has partial delve integration, but vim running inside tmux makes delve (and every other CLI tool) feel like it's already integrated. I don't use debugging that much with Go though.

Re: Visual Studio Code 1.9

#185

Post by hashhar »

chmln wrote: post #125
yokohummer7 wrote: post #38

This is an off topic, but I just learned from the article that PowerShell will soon be the default in place of cmd.exe in Windows 10. I welcome this change as I found the experience of using PS was superior to that of bash/zsh in general cases. But I hope they figured out the performance problem. As of writing, in the stable version of Windows 10, PS is perceptually slower than cmd, so I was forced to use PS only whe…

> the experience of using PS was superior to that of bash As a Linux dweller, I'm genuinely curious about this one. I've found PS inferior in just about any use case.

For one, I can do away with all of the text parsing that is prone to breakage in case a tool changes their output somewhat (or god help me - tools that can't handle unicode properly).

The power of bash actually comes from the GNU coreutils and other userland software. It has almost very little to with bash.

Try out bash on a busybox and feel the crippled effect.

Re: Visual Studio Code 1.9

#186

Post by kwood »

Tyriar wrote: post #20
yokohummer7 wrote: post #18

The slowness shown in the pre-1.9 terminal is a bit ridiculous. Was it really the case? I've never seen such a strangely-behaving emulator! Really good that they resolved the issue.

Hi, I worked on those improvements. Yes that is indeed what would happen when you ran a command with heaps of output, it would also lock up the UI while doing it. You probably haven't observed it much as you don't do recursive directory walk on a large directory ;) You can read more about the specifics if you're interested in https://github.com/Microsoft/vscode/issues/17875

The gained performance in the current release (and in Insiders for the past days) is huge - even without heaps of output. Those couple of milliseconds improved rendering time matter even if you "only" ls in a directory.

Thumbs up for this, Daniel. Thanks.

Re: Visual Studio Code 1.9

#187

Post by mixedCase »

st3v3r wrote: post #97
majkinetor wrote: post #85

Earlier quoted context omitted.

I would rather have devs invest time in serious functionality then doing stuff like GUI. Otherwise, this quickly turns to nonsence such as Nano server image builder [1] because Microsoft is still babysitting people who CBB to spend few hours to learn Powershell basics and need a GUI that generate 1 liner script. Microsoft should definitelly rise beyond click next culture. [1] https://blogs.technet.microsoft.com/nanos…

Discoverability and ease of use ARE serious functionality.

This: https://i.imgur.com/oPYr6Ch.png isn't discoverable?

The comments tell you in detail how each setting works (as you can see, they are even translated), you can search for a specific setting on the top, and it's categorized as well; defaults on the left, your own on the right.

Re: Visual Studio Code 1.9

#188

Post by hashhar »

yokohummer7 wrote: post #180
chmln wrote: post #125

Earlier quoted context omitted.

> the experience of using PS was superior to that of bash As a Linux dweller, I'm genuinely curious about this one. I've found PS inferior in just about any use case.

I had been a full-time Linux (desktop) user for more than 10 years, and only recently made a transition to Windows. As I'm nowhere proficient at using PowerShell I might be overrating it a bit, as the grass is always greener on the other side. Anyways, what I found to be satisfying while using PS were: 1. The input/output is done using objects. I know that "inter-process communication should be done with text" is the…

You seem to have articulated all my thoughts perfectly.

The thing about parsing text is a very huge pain point for me because I've had some tool change their output (and unicode issues) which broke some scripts.

The structured nature of PS makes it very powerful and allowed me to write a script that checks the latest versions of some software upstream and tells me if there are updates. I have that on bash as well but it's comparatively unmaintainable.

Re: Visual Studio Code 1.9

#189

Post by dragonwriter »

chmln wrote: post #125
yokohummer7 wrote: post #38

This is an off topic, but I just learned from the article that PowerShell will soon be the default in place of cmd.exe in Windows 10. I welcome this change as I found the experience of using PS was superior to that of bash/zsh in general cases. But I hope they figured out the performance problem. As of writing, in the stable version of Windows 10, PS is perceptually slower than cmd, so I was forced to use PS only whe…

> the experience of using PS was superior to that of bash As a Linux dweller, I'm genuinely curious about this one. I've found PS inferior in just about any use case.

PS is great if everything you are dealing with is built for the .NET ecosystem.

It's less great otherwise.

This makes it often great for working on Windows, and definitely great for working with Windows and other MS software that is designed for the .NET/PS world.

Post reply on HN