For about a year it has been my favorite editor when writing in Go and pretty much anything that's not Java.
I think the team behind it has been doing fantastic work. Thank you guys.
Visual Studio Code 1.9
261–270 of 312 posts
Re: Visual Studio Code 1.9
#262It's nicer than Atom and almost feels as snappy as Sublime. But Vim still is miles better when you have put in the work to become proficient. MacVim works great for retina screens and high color support.
The same is true for Neovim (and Vim 8?) in the terminal too.
Re: Visual Studio Code 1.9
#263I worked on the debug inline values feature. Let me know if you have any feedback/questions regarding that. Its currently disabled for evaluation purposes but you can enable in settings via "debug.inlineValues": true http://code.visualstudio.com/updates/v1_9#_inline-variable-v...
Thanks for all your hard work on this feature, it looks great!
Re: Visual Studio Code 1.9
#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.
Re: Visual Studio Code 1.9
#265VSCode + TypeScript is the perfect foot-in-door for MS to get into the web space. They're both excellent products by themselves, but also give Microsoft the platform to start dangling turnkey Azure integration in front of developers. Imagine if the IDE started to offer the ability to configure, deploy, and manage targeted production stacks--no browser / command line hackery required. That would be compelling.
You can do that right now if you use Azure ARM templates and set up project-level actions to run them through the Azure CLI. It's just a matter of someone bundling it together as an extension (I've been working on one, but solely for template snippets).
Re: Visual Studio Code 1.9
#266Earlier quoted context omitted.
Vscode is an IDE. It integrates all your development into one environment. It comes with support for version control, code editing, task running, and debugging all from one application.
From the FAQ: Visual Studio Code is a streamlined code editor with support for development operations like debugging, task running and version control. It aims to provide just the tools a developer needs for a quick code-build-debug cycle and leaves more complex workflows to fuller featured IDEs. So, even Microsoft doesn't think it's a full blown IDE. With enough plug-ins it certainly could be.
That last sentence strikes a chord. Most IDEs are basically heavy-weight plug-in platforms (especially Eclipse and IntelliJ), built with the intent of being heavyweight IDEs. The currently popular editors - ST, Atom, VS Code - and the console-based editors that are still popular - Vim, Emacs, etc - approach it from the other side, putting text editing (including search etc) first, then adding plugins on top of that.
Or maybe put differently, IDE's are enterprise software, editors are agile startups?
Re: Visual Studio Code 1.9
#267Earlier 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 learned C# with a big fat book, and the command line compiler... I understand the usefulness of command line applications. However, when I need more than what a simple shell script gives me, I'm more inclined to reach for node, ruby or python than C#/.Net ... the overhead for a quick scripting environment is quite a bit lower than having to setup a project and build requirements. I've done both... Why node, is simp…
Have you ever written a commandlet ? This is my point, regardless of how you feel in PS vs Bash or Python vs C# - exposing your application logic trough commandlets is incredibly simple and powerful - much simpler than doing a CLI app in other languages even with argument parsing frameworks in python and likes, commandlets let you pipe and return/accept .NET objects.
So my comment isn't PS everything or C# everything, it's if you're using C# to write a big fat monolithic app that has multiple isolated functionalities you can expose those fairly easily with PS.
Re: Visual Studio Code 1.9
#268Ohhhh 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.
Re: Visual Studio Code 1.9
#269VS Code's release notes are really nicely done - I don't usually comment on documentation but whoever wrote these did a bang up job!
I remarked this to my colleagues; part of me wishes they'd do faster releases, if only so that the changelog is smaller. Big lists of changes scare me. Big lists of changes that were apparently all done in a month and work without being horribly broken or half-assed, on the other hand, impress me.
This comment is a long-winded compliment.
Re: Visual Studio Code 1.9
#270Earlier 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'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.
Like I said above, my point was that PS lets you expose your app logic a lot easier than writing a CLI for it.