Live data from Hacker News

Visual Studio Code 1.9

code.visualstudio.com

191–200 of 312 posts

Re: Visual Studio Code 1.9

#191

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

Yeah, I know they all make use of godef, guru etc. but the way VSCode allows you to see declaration/documentation or full implementation on hover, integration with dlv etc. make it a nicer implementation for me than vim-go, but that's probably because I am not a ViM person myself.

Re: Visual Studio Code 1.9

#192
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 go back and forth between windows/unix for my day job and I also would be curious on any actual bullet points. I find that even in a situation where PS could potentially prove more useful or has an extra feature, what you end up with is a new set of chrome tabs open just to try and figure out how to do the thing. I suppose this might(?) be mitigated if you're embedded in the .NET world, but I just can't seem to get…

One of the best bits of PS1 advice I've seen was to get used to the Verb-Noun naming pattern [1] and in particular, the discoverability of the very standardized set of verbs [2].

Once you can guess the verb you want, then it can often be a simple matter of finding the right noun, and often nouns will be useful in sets similar to verbs.

Get-Verb, Get-Command, and Get-Help are all quite useful for looking for a command.

For dealing with the object pipeline I tend to find ConvertTo-Json very handy because as a developer I'm already quite used to reading objects in JSON already. (ConvertFrom-Json can similarly be used to bootstrap a PS1 pipeline with test data or remote data.)

[1] https://blogs.technet.microsoft.com/heyscriptingguy/2012/05/...

[2] https://msdn.microsoft.com/en-us/library/ms714428(v=vs.85).a...

Re: Visual Studio Code 1.9

#193

Am I alone in rejecting this new wave of Electron/node-webkit based text editors? Every single one I've tried has been horribly slow, unstable, and a giant resource hog. I gave Atom a shot, and it crashed on importing a .csv file of a few thousand lines. What I want from a text editor is simply that: a text editor. For anything more advanced, move up to a proper IDE. Why anyone uses these over something like Sublime…

My main laptop broke down and I'm currently using a Pentium Dual Core T3200, 3GB of RAM, an HDD... in other words, a pretty damn old laptop.

I knew VSCode was very optimized for an Electron application, but you have no idea how fast this is. This is faster than my Vim set-up, and I have taken my sweet time making sure Vim only loads the plugins it strictly needs and I try to switch to the asynchronous version of a plugin as soon as it pops up but still, VSCode is more consistently responsive for a lot of tasks.

I'm not sure wether I'll make a full switch yet, specially once I get a proper computer back, but the quality of the plugin ecosystem (I thought vim-go was amazing, but VSCode's Go plugin is just ridiculously good and properly asynchronous) coupled with this huge performance surprise are really making me consider it.

Re: Visual Studio Code 1.9

#194
post #43

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 a web dev IDE. Microsoft has lost the mobile platform wars and pushing the web is a way of countering that. Plus, web and azure do go hand-in-hand, as you point out.

Python and CloudFormation here. Others swear by the Golang support.

Re: Visual Studio Code 1.9

#195
post #90

Earlier quoted context omitted.

VSCode vs Atom (in my opinion) isn't even a contest. Maybe Atom is super nice for some web dev stuff, but as a full flown IDE I just don't see the features.

Are you confusing VSCode with Visual Studio? VSCode is not an IDE, it's an editor, much like Atom.

If there's some sort of editor-IDE spectrum, VSCode likely lives closer to the IDE side than editor.

Re: Visual Studio Code 1.9

#197

I have a new project at work that I decided to use it for to see how I liked using VS Code. For the most part, I like it, but it's lack of Mac-nativeness bugs me, and it may bug me enough to switch. Double clicking the window bar in all natives app minimizes them to the dock for me. In Visual Studio, it maximizes my window (but not into full screen mode). I keep clicking the menu bar to minimize a window, and this ke…

There is a way to set VScode to use the native menu bar on macOS instead of the Electron'd frameless bar.

Enabling that system-wide made the experience so much more pleasant:

    "window.titleBarStyle": "native",

Re: Visual Studio Code 1.9

#198
post #130
post #34

Am I the only one who misses an apt repository?

You can use ubuntu-make, but it doesn't seem (to me) any easier than grabbing the .deb file...

The point of having it in a repository is not managing it through apt, but updating it without having to manually download deb files...

Re: Visual Studio Code 1.9

#199

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…

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?

Re: Visual Studio Code 1.9

#200

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

An IDE is so much more. For instance, refactoring features. Even Microsoft defines VSCode as a "code editor" and not an IDE.

Have you even used VSCode?

It has refactoring, and revision control integrated. You can compile and run code, you can set breakpoints and step through execution. That's waaaaay more than just an editor.

Post reply on HN