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

Visual Studio Code 1.7

code.visualstudio.com

Post reply on HN
Print view View original

171–180 of 180 posts

Re: Visual Studio Code 1.7

#171

Post by sumsted »

neves wrote: post #125

I couldn't find a good tutorial about using VSCode for Python development. I'd like to setup debugging, intellisense and the interactive shell, but the info is sparse. Do you have any suggestion?

I'm thinking of moving away from pycharm when this year runs out and moving to vs code + python. It has full debug, scm, virtualenv support (which was broken in pycharm 2016.x for a time) and intellisense. I would still use Brackets for html and css because I love quick-edit, the ability to edit a css rule or color by hovering and hitting ctl-e.

Re: Visual Studio Code 1.7

#172

Post by tonyplee »

vially wrote: post #157
tonyplee wrote: post #136

Earlier quoted context omitted.

You should try Digital Ocean $5/month. Have root access, etc. Is there a shared host cheaper than that?

I don't know if there is any shared host cheaper than that (I suppose there are but I'm too lazy to check right now), but sometimes the appeal in using a shared host is in some of their features which you don't get in a VPS (e.g.: cpanel).

Also be very careful, with "Dirty COW" hack, anyone can become root as long as they can run their own binary on any shared host.

Re: Visual Studio Code 1.7

#173

Post by Maken »

forgetsusername wrote: post #55

Not a negative comment in the thread so far. That's amazing for something Microsoft, as anyone who's been around here can attest. There's a corner being turned here; time to buy MSFT?

My only complain is that they still don't allow mixing vertical and horizontal layout splits. That aside, VSCode is a quite good code editor.

Re: Visual Studio Code 1.7

#174

Post by Maken »

kid0m4n wrote: post #117

They had to rollback the update: > Unfortunately, we needed to roll back the 1.7 release of VS Code. One of the great new features in 1.7 is the automatic acquisition of typing files when writing JavaScript and TypeScript. These typings files drive the IntelliSense (code completions) experience in the tool. The feature was so great that we started to overload the npmjs.org service. The right thing to do in the short…

They already published a recovery build. Now updating 1.7 will install 1.7.1.

Re: Visual Studio Code 1.7

#175

Post by komali2 »

scott_karana wrote: post #114
komali2 wrote: post #40

Earlier quoted context omitted.

The biggest thing for me has been the consistency. They already had an amazing IDE (Visual Studio), then they buckled down and made an amazing paired-down version (VSCode). It works well, does all the things I'd want and then some. Compare to Google releasing a chat client / message handler (google voice app), another one (hangouts), taking away functionality (removing shared sms/hangouts convos), then releasing two…

> an amazing paired-down version FYI, and no judgement: the word is "pare", meaning "to trim" or "to cut down". Also seen in "paring knife" :-)

Hah, thank you. I also always confuse "here here" and "hear hear," amongst a million other things.

Would you believe I spent 4 years getting a Bachelor's in Writing? :P

Re: Visual Studio Code 1.7

#176

Post by hashhar »

Achshar wrote: post #126
komali2 wrote: post #33

Ah haha this is too funny, I just this morning caved from trying to have a functioning version of Ubuntu on the macbook work gave me, booted back into OSX, and spent a good 30 minutes scrolling through the VSCode keyboard shortcuts JSON, writing down the ones I was interested in relearning on post-its and lining them around my monitor. And not four hours later they release a pretty little printable PDF. Not very on t…

It's not like it was very difficult to have a simple key binding list before the update. There are many json to html table websites out there, or you could just paste it in vs code and use multiple cursors to remove all the json syntax in like 10 seconds.

No, you use regexes for that.

Re: Visual Studio Code 1.7

#177

Post by hashhar »

headmelted wrote: post #164

I'm currently working on nightly builds for ARM and Intel linux-based systems (including Raspberry Pi and [Chromebook, Android] I could really use one or more Raspberry Pi 2/3 testers on a Debian distro (ideally Raspbian) for early feedback. Hoping to announce the project on HN properly myself when it's ready (it's a very early state, although extensions are working), so I'd ask for discretion of whoever feels like h…

Try posting to reddit. On the respective product subs.

Re: Visual Studio Code 1.7

#178

Post by neves »

sumsted wrote: post #171
neves wrote: post #125

I couldn't find a good tutorial about using VSCode for Python development. I'd like to setup debugging, intellisense and the interactive shell, but the info is sparse. Do you have any suggestion?

I'm thinking of moving away from pycharm when this year runs out and moving to vs code + python. It has full debug, scm, virtualenv support (which was broken in pycharm 2016.x for a time) and intellisense. I would still use Brackets for html and css because I love quick-edit, the ability to edit a css rule or color by hovering and hitting ctl-e.

PyCharm community edition is very good. Maybe all the features aren't necessary. But VSCode would allow me to use it in other environments.

Re: Visual Studio Code 1.7

#179

Post by nixos »

scott_karana wrote: post #152
nixos wrote: post #119

Earlier quoted context omitted.

What I also don't understand is why doesn't Debian package it? Is it not fully free or does it have licencing issues like Atom?

It would need a maintainer, and would have to work its way through unstable->testing->stable too. Is there even an official Debian that runs of RasPi, anyways? Thought Raspbian was a fan effort that resurrected an old armf fork or similar.

https://michaelfranzl.com/2016/10/31/raspberry-pi-debian-str...

Re: Visual Studio Code 1.7

#180

Post by orbitingpluto »

mook wrote: post #149
tw04 wrote: post #146

Earlier quoted context omitted.

Umm, you can disable it globally. They have pretty amazing documentation, 3 seconds of searching later: http://vscode-docs.readthedocs.io/en/stable/supporting/faq/#... Windows Close VS Code. Open the command prompt. Type cd %ProgramFiles(x86)%\Visual Studio Code\resources\app Type notepad product.json Replace enableTelemetry=true with enableTelemetry=false. Save the file via CTRL+S and exit Notepad. Collection of usa…

The current docs ( https://code.visualstudio.com/Docs/supporting/FAQ#_how-to-di... ) seems to indicate that it's just a normal pref now, you don't need to edit the app to do it. I wasn't able to figure out what version readthedocs was last generated for.

Telemetry and crash report still enabled by default. Unsure of what will happen upon update if the global settings file is altered.
Post reply on HN