I remember Rob making a comment that .Net is his most popular topic.
From a dotnet point of view, it is much easier for many programmers to watch videos instead of reading a book. For one, language is not as big a barrier because you have a visual example to go along with his narrative.
The biggest problem I personally have with dotnet is the necessity to know all the nuances of whichever stack you are developing on.
In learning MVC, Rob goes over every single issue a programmer may have in creating a web site, circumventing those moments where you get stuck trying to find out how to change how routing works. He also goes over a token based login that completely throws out the default dotnet implementation.
In addition, he goes over creating a support site, dependency injection, and lots of other things that you would have to be an active member of the MVC community to even know it existed.
He even posts his code to github. Basically, Rob acts as a mediator between the dotnet world and the open source linuxy way of doing things. Many of his comparisons are with Ruby on Rails. When I talk with people I know who code in C#, they hardly spend time reading about new trends in HTML and javascript and prefer to get the easy way by learning the dotnet way of doing things.
As a dotnet developer, you (and me too) put yourself into a position of ignorance. Then you wait for someone more senior to come out with a simple method that you could use for rapid prototyping. You rely on that senior person not because you can't code but because you really don't know the nuances of the framework you are leaning on. This refusal to learn the bare bones of HTML and adopt some micro framework creates the phenomenon where you are kind of hosed into grabbing the quickest path to productivity.
Edit: I edited quite a few things for clarity. Probably shouldn't submit so fast.