The problem that I have with VSC releases is that they are automatic, and I don't want to screw up my current workflow when I reset the application for an update. I have wasted hours before with VSC updates.
Visual Studio Code 1.9
141–150 of 312 posts
Re: Visual Studio Code 1.9
#142Earlier quoted context omitted.
https://code.visualstudio.com/docs/languages/cpp > VS Code supports tasks that you can configure to build your application, and natively understands the output of MSBuild, CSC, and XBuild.
Yes, building works well. But how do you run your application? (To be clear I'm asking what workflow users use personally, since it seems like nobody else has this issue.)
For me, I build on the command line, because I have a funky build process, and then when I want to debug it I just press the 'debug' button.
There's a big JSON file with the debug configurations, and a drop-down to allow you to select which one is active. Each gdb debug configuration lets you specify the usual binary path and command line arguments, plus a whole lot of other configuration I haven't looked at. I haven't had to do any project-style setup --- it just magically finds all my source files.
It looks like it supports gdb on Windows and Linux and lldb on OSX (only ever tested on Linux, though). Out-of-the-box you get sample configurations to both run and attach to a C/C++ binary.
gdb integration is pretty seamless; breakpoints, conditional breakpoints, stack traces, local and global variables. Haven't seen threads, watchpoints, or an assembly window yet. There's a debug console, but entering commands doesn't appear to send them to gdb.
It's one of the best Linux gdb environments I've seen (even though most gdb integrations are terrible).
Re: Visual Studio Code 1.9
#143Earlier quoted context omitted.
Do you have any proof that it is astroturfing and not just genuine enthusiasm? I am almost a lifelong vi user, but have been using Visual Studio Code last few months because it's Rust experience is smooth. (Though Emacs seems to do well as well.)
Just that the sentiment scores of comments blow everything else out of the water. Haven't done one in a month or two though.
>Just that the sentiment scores of comments blow everything else out of the water. Haven't done one in a month or two though.
Well, that's how a product that does things right would look like.
That is, if "Sentiment scores" wasn't mumbo jumbo crap -- isn't the social sentiment-analysis fad from 5-7 years ago over everywhere yet?
Re: Visual Studio Code 1.9
#144This 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…
Yeah, the new Powershell will be very fast AFAIK. They had to do it because nano server was starting faster then Posh which was ridiculous.
Re: Visual Studio Code 1.9
#145Earlier quoted context omitted.
They lost the mobile phone, but I bet they will win the hybrid tablet/netbooks one, given how Android tablets disappeared from many consumer shops here in Germany, only to be replaced by Windows 10 ones. Samsung and Asus ones seem to have been the surviving brands and even they have Win10 devices on their brand sections.
> They lost the mobile phone, but I bet they will win the hybrid tablet/netbooks one, given how Android tablets disappeared from many consumer shops here in Germany, only to be replaced by Windows 10 ones. That could just be a regional anomaly.
Then it is an European regional anomaly, because I have seen it in other countries that I visit regularly (southern Europe).
On the other hand, speaking about regional anomalies, I almost never seen Chromebooks on sale, or people using them. Yet they apparently sell like hot cakes in US.
Re: Visual Studio Code 1.9
#146This 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.
I used majority of mainstream shells and Posh is a scpace ship compared to any other in existence. I wont reiterate again and again why, there are planty of places eihter on HN, reddit or SO why is it so. I guess you will have to give it a serious try.
Re: Visual Studio Code 1.9
#147Earlier quoted context omitted.
They lost the mobile phone, but I bet they will win the hybrid tablet/netbooks one, given how Android tablets disappeared from many consumer shops here in Germany, only to be replaced by Windows 10 ones. Samsung and Asus ones seem to have been the surviving brands and even they have Win10 devices on their brand sections.
No they won't. No one wants to use clunky non touch optimized windows desktop apps on a tablet. Besides, UWP was a failure.
Ever heard of Project Centennial?
Or the fact that all new APIs are mostly UWP only?
Re: Visual Studio Code 1.9
#148Earlier 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've used both extensively and I think they are fairly different, with different strengths and weaknesses. Bash is more pragmatic and more concise on the command line. PS is more uniform in its design and nicer for scripting IMO. It allows passing objects through pipes, has built-in JSON reading and writing, built-in parameter handling with defaults, mandatory and optional params, switches etc., and such niceties.
Bash is not more concise, its other way around, of course, if you use default aliases. The reasons is logical - you almost never use text parsing in Posh while you almost never have anything without it in bash.
Re: Visual Studio Code 1.9
#149Earlier quoted context omitted.
Or maybe it's a good product? Occam's Razor and all that.
This is the only product on HN I've ever seen where "This is great!" is all over the place and never downvoted. Almost every single product on HN that makes it to the front page is full of flamewars and grumps. I should post the sentiment scores. Its a serious outlier.
>This is the only product on HN I've ever seen where "This is great!" is all over the place and never downvoted.
Then you probably weren't on HN for long, because all kinds of upcoming products used to have a similar treatment (Rails/Ruby at some point, then Golang, then Mongo, then Nodejs, nowadays Rust, etc.).
But unlike a language, which might have people for or against it with strong opinions, who would downvote a new code editor that's not part of a religious war (like vi/emacs) and that does things mostly right?
>I should post the sentiment scores
How about you stop doing sentiment analysis, instead? It's a crappy "data mining" where you can find everything you want to find, and next to useless for any actual insight.
Re: Visual Studio Code 1.9
#150Earlier quoted context omitted.
Atom and Dolphin also get near-unanimous praise when they come up. It's not exclusive to VSC.
With Atom, there were usually many gripes about sluggishness. Maybe that's improved with recent updates.
Atom is also actually sluggish, so the gripes make sense. VSC isn't.