&gt; This will have to be very good to be better than Visual Studio on Windows.<p>Really?  I feel MS has really dropped the ball with VS.  VS2013 was OK, but not great.  A lot of random lock-ups in really annoying situations where you can&#x27;t even fathom why (like opening a text file).  VS 2015 is actually awful - it wasn&#x27;t until Update 1 that typing this (below) in C# would pop-up an on screen exception dialog:<p><pre><code>    class Foo : Bar
    {
        public Foo()
           :
</code></pre>
Pressing enter after the colon would throw the exception consistently.  How on earth was that missed in testing?  This is such a common C# pattern for invoking the base or this constructor.<p>I often find myself staring at the screen, saying in my head &#x27;What the hell are you doing now!&#x27;.  The new DNX project system is unusably slow (compiling) and the tooling for it is non-existent.  And for me it still crashes all of the time.  Other devs on my team are having similar problems.<p>TFS and TFS explorer is a total joke.  The &#x27;offline mode&#x27; is slower than online mode, and also causes crashes.  If I lose my VPN connection then I have to shutdown VS and restart before TFS will reconnect again (this has been an issue for every version of VS I&#x27;ve used).  Luckily we&#x27;re moving away from that travesty of a system to git very soon (the VS git integration is actually pretty good).<p>I used to feel that VS was a really solid piece of tooling, and I agreed with your sentiment that I quoted.  I don&#x27;t any more.  I will check this out, and if it works then I&#x27;ll happily drop VS, two years ago I couldn&#x27;t ever imagine myself saying that.<p>Competition can only be a good thing here.