<story><title>Visual Studio 2013 released to web</title><url>http://blogs.msdn.com/b/visualstudio/archive/2013/10/17/visual-studio-2013-released-to-web.aspx</url></story><parent_chain><item><author>727374</author><text>This rant has been brewing for many years...&lt;p&gt;Everything&amp;#x27;s been downhill since VS6.  I&amp;#x27;m only joking, but seriously, does anyone remember how lightning fast VS6 was?  That was over 15 years ago with much slower computers.  I guess application &amp;#x27;snappiness&amp;#x27; has not been a priority for the Visual Studio decision makers.&lt;p&gt;I&amp;#x27;ve used VS since the late 90s (writing node.js in ST2 now) and honestly appreciate the hard work and cool features that goes into it.  The new VS2013 feature that shows how often a function is referenced is useful.  I don&amp;#x27;t get that in ST2 and probably never will.  But I&amp;#x27;ve used VS enough that I&amp;#x27;ve become philosophically opposed to it and other similar IDEs.  The core of the problem for me was that all the fancy wizards and project templates are not maintainable for MS.  There were a number of times I was using some new project type introduced in a version of VS only to find the template was incompatible in the &lt;i&gt;next&lt;/i&gt; version (e.g. reporting in 2005).  This inevitably lead to a lot of unexpected work when my team would upgrade.  Many of the productivity wizards impose hidden debt on their users.&lt;p&gt;Another major gripe was that VS would get really sludgy for solutions with a great number of projects&amp;#x2F;files.  Take note that whenever you see MS demo a hot new feature, it&amp;#x27;s always with a very simple solution.  Also, VS would block for me a lot, but that was probably due using too many plugins.  I&amp;#x27;d find that an application freeze of even 2 seconds would distract me.  Not an issue I face now with a text editor + repl.&lt;p&gt;&amp;lt;&amp;#x2F;rant&amp;gt;</text></item></parent_chain><comment><author>overgryphon</author><text>I think you may have selective memory with regards to VS6 (understandable over 15 years). Having recently worked at a company that for silly reasons did not upgrade beyond VS6, it was not lightning fast, took several minutes to open, and crashed frequently even with smaller projects.&lt;p&gt;Modern VS really needs to work on managing large projects- but this isn&amp;#x27;t something it ever had to begin with, and has certainly improved since VS6 despite added functionality. The responsiveness issues you list seem a little more problematic than normal from my experiences- I would definitely try uninstalling a few plugins and seeing if that helps.</text></comment>
<story><title>Visual Studio 2013 released to web</title><url>http://blogs.msdn.com/b/visualstudio/archive/2013/10/17/visual-studio-2013-released-to-web.aspx</url></story><parent_chain><item><author>727374</author><text>This rant has been brewing for many years...&lt;p&gt;Everything&amp;#x27;s been downhill since VS6.  I&amp;#x27;m only joking, but seriously, does anyone remember how lightning fast VS6 was?  That was over 15 years ago with much slower computers.  I guess application &amp;#x27;snappiness&amp;#x27; has not been a priority for the Visual Studio decision makers.&lt;p&gt;I&amp;#x27;ve used VS since the late 90s (writing node.js in ST2 now) and honestly appreciate the hard work and cool features that goes into it.  The new VS2013 feature that shows how often a function is referenced is useful.  I don&amp;#x27;t get that in ST2 and probably never will.  But I&amp;#x27;ve used VS enough that I&amp;#x27;ve become philosophically opposed to it and other similar IDEs.  The core of the problem for me was that all the fancy wizards and project templates are not maintainable for MS.  There were a number of times I was using some new project type introduced in a version of VS only to find the template was incompatible in the &lt;i&gt;next&lt;/i&gt; version (e.g. reporting in 2005).  This inevitably lead to a lot of unexpected work when my team would upgrade.  Many of the productivity wizards impose hidden debt on their users.&lt;p&gt;Another major gripe was that VS would get really sludgy for solutions with a great number of projects&amp;#x2F;files.  Take note that whenever you see MS demo a hot new feature, it&amp;#x27;s always with a very simple solution.  Also, VS would block for me a lot, but that was probably due using too many plugins.  I&amp;#x27;d find that an application freeze of even 2 seconds would distract me.  Not an issue I face now with a text editor + repl.&lt;p&gt;&amp;lt;&amp;#x2F;rant&amp;gt;</text></item></parent_chain><comment><author>nightski</author><text>I disagree heavily.  Stock VS is very fast.  However it does slow down significantly when using a plugin like ReSharper.&lt;p&gt;But for me in the end it is worth it.  Show me any text editor or IDE that provides the same number and quality of productivity enhancing features as ReSharper that isn&amp;#x27;t as slow or slower.</text></comment>