Moving back to .NET

[rumbu via Digitalmars-d]

On Friday, 25 September 2015 at 09:05:31 UTC, John Colvin wrote:
> On Friday, 25 September 2015 at 08:59:17 UTC, Jonathan M Davis 
> wrote:
>> On Friday, 25 September 2015 at 08:53:41 UTC, John Colvin 
>> wrote:
>>> On Friday, 25 September 2015 at 07:26:13 UTC, rumbu wrote:
>>>> Starting Visual Studio on my machine takes 2 seconds,
>>>
>>> What magic are you doing to achieve this? It has always taken
>>> >30 seconds on mine.
>>
>> LOL. On my work computer (which is no slouch), it takes 
>> something like two or three minutes to actually be usable, 
>> where it's frozen, saying "not responding." gvim, on the other 
>> hand, starts instantly.
>>
>> - Jonathan M Davis
>
> Yeah that >30 seconds was probably being generous. It's quite 
> rare to see <60.

Sorry, I was wrong, below 2 seconds, measured using Passmark 
AppTimer:

Visual Studio 2013 Ultimate - 5 executions
C:\Program Files (x86)\Microsoft Visual Studio 
12.0\Common7\IDE\devenv.exe - 5 executions
1.3741
1.2808
1.3419
1.2802
1.3440

Loading a complex C# solution (11 projects - ASP.NET web server, 
Silverlight client, Android client, various libs, 60 kloc) - 9 
seconds.

Windows 10 64 bit, Intel Core i7 3612QM, 16G RAM, SSD.

Now, comparing this to the timings you posted, I understand why 
you prefer to use the command line and text editors. Me, I don't 
have *any* reason to go back in time 20 years ago, I hate that 
black & white thing on my screen.