News for hackers. Stuff that matters.
[dead]
Re:Visual Studio Code 1.0 by wlesieutre on Thursday April 14, 2016 @03:35PM (#11499702)
Googled part of this for you:

>Why not just set up atom to use your existing corporate proxy?

"Many of these text editors support proxy servers, but none of them that I have tried support NTLM for authentication and if your corporate proxy is using NTLM they simply cannot connect to it. Or lets say not directly! Actually the only solution I have found is to use a software called CNTLM that can act as a proxy server itself and behind the scene it can connect to another proxy server that is using NTLM." [1]

As to what needed a compiler, that part I'm not sure about. Aren't Atom extensions generally in javascript? Could it have been the CNTLM installer that wanted a compiler?

[1] https://devinthefastlane.wordpress.com/2015/12/24/how-to-ins...

Re:Visual Studio Code 1.0 by hhandoko on Friday April 15, 2016 @01:17AM (#11502357)
NTLM auth is but one of various other roadblocks in a corporate environment.

In my previous job, the company runs a MITM proxy, it broke SSL checks for package managers. You ended up having to disable SSL checks and load up company-issued certs.

I asked whether we can find a solution to this issue on the company forum, as there are other developers and data analyst whose life can be made easier if this just works, the response I get was: "just download them manually", I kid you not.

Re:Visual Studio Code 1.0 by viraptor on Friday April 15, 2016 @03:29AM (#11502772)
Sigh... corporate proxies are the worst software I ever had to deal with. Terrible for productivity. Enough that people bring in own 3g dongles and connect to that wifi instead. Whole audit/security defeated :(
Re:Visual Studio Code 1.0 by neves on Thursday April 14, 2016 @04:20PM (#11500023)
I thought they were, but the simple installation of the column select mode failed with a message of missing compiler. I don't want to delve inside my editor internals.

The first difficult thing is to discover that I have to install the sublime-style-column-selection package. So it failed and didn't researched more.

Re:Visual Studio Code 1.0 by neves on Thursday April 14, 2016 @05:19PM (#11500436)
Ops, I've just tried it to see the error message and it worked! The sysadmins just updated a lot of Windows patches, maybe it solved the problem. BTW: VSCodes starts a lot quicker than Atom.
Re:Visual Studio Code 1.0 by Arnavion on Thursday April 14, 2016 @04:44PM (#11500198)
Coffeescript compiler?
Re:Visual Studio Code 1.0 by voltagex_ on Friday April 15, 2016 @09:07AM (#11503933)
Please report issues instead of using things like CNTLM - it has at least one bug that causes crashes under heavy traffic and may require you to store your password/hash in an insecure way.
Re:Visual Studio Code 1.0 by coredog64 on Thursday April 14, 2016 @04:06PM (#11499908)
I have admin and can install anything locally, but also I can't get any Atom packages to install from behind our proxy. That's okay -- I just wait until I have my laptop on my WiFi network at home and everything is copacetic.

It's not just me -- we had a trainer giving a class, & this guy lived and breathed Atom and he couldn't install an updated version of an existing package from our network either. His solution was to tether his phone.

Re:Visual Studio Code 1.0 by taude on Thursday April 14, 2016 @04:21PM (#11500031)
I have the same problem with the Atom packages behind the proxy. I had to do some npm and git configuration to add http_proxy. It worked for a bit, then the corporate password changed, and I never really updated the buried settings.

I'll probably have a pretty easy time getting the MSFT Visual Studio Code approved for machine installation for devs on my team, even though we're an Eclipse/Java shop. I've been trying to get everyone normalized on a JavaScript editor, since the tools we have in Eclipse are severely lacking.