Just for the record, in ASP.NET you can use many tools to combine (and minify) scripts and stylesheets [1][2]. Generally, these do not require the use of a command line.
To be fair, the majority of .NET developers depend on the tooling provided by Microsoft, which consists mainly of Visual Studio. The tools from Microsoft go a long way to isolate developers from using the command line, although the recent addition of NuGet to the toolset has also introduced the Package Manager Console [3] inside of Visual Studio.
Yup I know. That's what made this blog post somewhat frustrating. The author clearly has no depth with javascript or front-end web development.
However perhaps I was a bit harsh. While these are not particular valid or well reasoned points about javascript, they are still a common first impression javascript leaves on many developers. Perhaps it still does speak to deeper problems with javascript as a language.
To be fair, the majority of .NET developers depend on the tooling provided by Microsoft, which consists mainly of Visual Studio. The tools from Microsoft go a long way to isolate developers from using the command line, although the recent addition of NuGet to the toolset has also introduced the Package Manager Console [3] inside of Visual Studio.
[1] http://www.nuget.org/packages/Microsoft.Web.Optimization
[2] http://www.nuget.org/packages/Cassette.Web
[3] http://docs.nuget.org/docs/start-here/using-the-package-mana...