> all of its crashes have been 100% my fault.

Wait, what? Why is it okay if a program crashes at all?

... can you show me a program you've written that accepts complex developer input and literally never crashes?

Microsoft shouldn't be held to the same quality standards as a hobby programmer.

Okay, but what I'm saying is that you are holding them to an impossible standard. If you believe perfect programs exist, I've got news for you.

Development environments in particular may have to crash sometimes in order to prevent the user from wrecking everything else on the system.

OK then let's compare VS to XCode, which doesn't even have half the features of VS and crashes twice as much. If not, which comparable product would you pick?

Running tons and tons of VS instances while debugging broken, memory hogging programs, modifying the XML for weird project types for third party plugins poorly, etc. Things that MS really can't do anything about.

I've never seen a GUI form builder that really worked that well, but the WinForms and especially WPF builders are huge dogs.

Less said about the old-fashioned WebForms GUI, the better...

I would have agreed that it's a good product right up to Visual Studio 2013. But Visual Studio 2015 is slow, buggy and unstable. They really have screwed something up, it has been months, and the update pack they released didn't make any tangible improvements. Meanwhile the "extensions and updates" area just continues to push Microsoft products I don't need, and every now and then I am not allowed into the IDE because my license has "gone stale". Everyone in my team has daily crashes, bugs and slowdowns and it is hurting us. How can Microsoft not have found any of these issues during all their testing?