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

271–280 of 312 posts

Re: Visual Studio Code 1.9

#271

Post by Yaggo »

christophilus wrote: post #30

VSCode really does improve with each release, and the monthly cycle is just about the perfect pace. This is a great example of how to run an OSS project. I wonder how much Microsoft spends on it each month, and what value they see in it? Is it just a marketing expense? e.g. They fund VSCode in order to gain the good will of developers which they hope will turn into Azure or maybe Windows sales in the future?

> They fund VSCode in order to gain the good will of developers which they hope will turn into Azure or maybe Windows sales in the future?

I think they are just trying to make Windows (and Microsoft) more relevant among web/foss developers by making sure that top-notch tools exist with first-class Windows support, so this falls to same category as Windows Subsystem for Linux.

Re: Visual Studio Code 1.9

#272

Post by will_hughes »

flukus wrote: post #254
will_hughes wrote: post #250

Earlier quoted context omitted.

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.

Well yes, that's an example that's relying on the find utility, for which the equivalent in the windows world (at least for file management) is robocopy.

    robocopy /r $pathFrom $pathTo *.html
If you wanted to exclude say 'main.js' then it'd be:

    robocopy /r $pathFrom $pathTo *.html /xf main.js
..and /xd is for excluding directories too.

I guess copy-item should be smarter to be able to handle this.

Also, for what it's worth, your example in the linked post is a bit more verbose than it really needs to be. You're comparing a full-up programming language to nant there. So yeah, it's a bit more verbose there. But I bet I can come up with a counter-example where nant is a giant nightmare to get right (or requires just dropping straight to executing external commands) (There's a reason I've killed off all usage of nant years ago, and gone to powershell for build scripts)

Re: Visual Studio Code 1.9

#273

Post by will_hughes »

vgy7ujm wrote: post #257
will_hughes wrote: post #250

Earlier quoted context omitted.

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

> Perl is a full blown general purpose programming language with a massive collection of libs and frameworks.

> So Bash is also very powerful with the help from all its friends

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

All of these things are also true for Powershell. Powershell can use any .NET Assembly, and if necessary make native windows system calls too if you really want.

Re: Visual Studio Code 1.9

#274

Post by nol13 »

nikcub wrote: post #173
christophilus wrote: post #30

VSCode really does improve with each release, and the monthly cycle is just about the perfect pace. This is a great example of how to run an OSS project. I wonder how much Microsoft spends on it each month, and what value they see in it? Is it just a marketing expense? e.g. They fund VSCode in order to gain the good will of developers which they hope will turn into Azure or maybe Windows sales in the future?

VS Code is part of the strategy to get .NET Core distributed and to support the web layers built on top of that which mostly now use open source technology (from npm and bower through to grunt, typescript and angular)

Na, I think the real plan starting to unfold. This week we get the new welcome screen, next will be the "deploy to Azure" and "how to make a Windows Store App" sidebar links.

(not that I'll stop using it, I'm sure someone will fork if gets too obnoxious)

Re: Visual Studio Code 1.9

#275

Post by Matthias247 »

santaclaus wrote: post #10

VS Code's release notes are really nicely done - I don't usually comment on documentation but whoever wrote these did a bang up job!

Absolutely! I love to read through them on each release to discover whats new. And each time I'm surprised how many new useful things get integrated.

Re: Visual Studio Code 1.9

#276

Post by rubber_duck »

chadgeidel wrote: post #199
rubber_duck wrote: post #181

Earlier quoted context omitted.

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…

I've been dabbling with PS (using it as my primary console) but my workflow just isn't that complex, so I don't have a compelling reason to write cmdlets (yet!). Can you recommend a good tutorial?

I've used MSDN docs but I wouldn't call that a tutorial :)

Re: Visual Studio Code 1.9

#277

Post by nikon »

CyanLite2 wrote: post #224
christophilus wrote: post #30

VSCode really does improve with each release, and the monthly cycle is just about the perfect pace. This is a great example of how to run an OSS project. I wonder how much Microsoft spends on it each month, and what value they see in it? Is it just a marketing expense? e.g. They fund VSCode in order to gain the good will of developers which they hope will turn into Azure or maybe Windows sales in the future?

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

Project Rider?

Re: Visual Studio Code 1.9

#278

Post by simooooo »

sdoering wrote: post #268

Ohhhh I love the new 'Synchonized Markdown" feature. This will in the end replace the need for iA writer (that I happily paid for) on my machine. As I do have a workflow already setup to (Semi-)automate creation of files from .md I now can do this inside VSC and do not need to open another application.

Thanks for bringing this feature up.. I had no idea the markdown preview feature even existed!

Re: Visual Studio Code 1.9

#279

Post by blunte »

I am super pleased that VS Code exists, works on multiple platforms, and is apparently a first class project at MS Dev. Like some other devs, I ran as far from Microsoft as I could many years ago... but now it seems they are trying to be more open, or less protectionist/monopolistic.

I used VS Code (starting at v1.5) for a couple of projects (on my Mac), and I found it quite effective and very performant. The performance, particularly the interface latency, is a big complaint I have with other "fat" IDEs. And while my hands still try to do some Vi commands and a lot of Emacs commands, I found the keyboard options for VS Code acceptable.

This is as close to a Thank You to Microsoft that I have uttered in a long time. I hope they keep up the good work.

Re: Visual Studio Code 1.9

#280

Post by riejo »

rado wrote: post #264

"Format on Paste" could convert me from Coda, but it doesn't seem to work. macOS, HTML mode, enabled the option, restarted, doesn't format until I manually execute the Format Document command.

That's most likely because the html formatter doesn't support to format range/selection but only the full document.
Post reply on HN