Zombie Operating Systems and ASP.NET MVC

Interesting write up, and a nice style.<p>The filename limitation isn't the only problem. There's also a limit of 260 characters in the URL.<p><a href="http://stackoverflow.com/questions/265251/asp-net-url-maxpath-limit" rel="nofollow">http://stackoverflow.com/questions/265251/asp-net-url-maxpat...</a><p>Boo-sucks if you suddenly run into that without expecting it!

&#62; But ASP.NET MVC was based on ASP.NET. Which checks for the existence of a file before running any scripts.<p>This is not correct. When you configure an ISAPI filter in IIS, such as ASP.NET or PHP, you can choose whether or not to verify the presence of files. You can also do this via configuration for .NET HTTP handlers. Parts of ASP.NET itself rely on this feature, such as the trace.axd handler and the web resource handlers.<p>I don't have the option to verify that you can't create those routes, but if you can't, it's not related to that particular feature.

This article (and the comments on it here) is a pretty classic illustration of the "damned if you do, damned if you don't" situation Microsoft (and any other company that at least attempts to preserve backwards compatibility) inevitably ends up in.

Reminded me of this Snopes piece about the width of space shuttle parts being determined by the size of a horse' butt. <a href="http://www.snopes.com/history/american/gauge.asp" rel="nofollow">http://www.snopes.com/history/american/gauge.asp</a><p>Technology may not be immune from the stubbornness of standards that no one feels inclined to change.

I couldn't believe the kludginess of Windows did run that deep - I had to check it out: <a href="http://www.dieblinkenlights.com/blog_en/the-unbearable-kludginess-of-windows" rel="nofollow">http://www.dieblinkenlights.com/blog_en/the-unbearable-kludg...</a><p>And what's the matter with the "all extensions" thing?<p>/me ducks and says goodbye to karma.

Thank God for *nix based systems

The legend continues.

Honestly the fact that you couldn't user certain filenames in the URL wasn't as big a problem, it was the fact that you couldn't do URL rewriting unless you wrote your own httphandler that annoyed me the most. MVC does an awesome job with regex based URL routing. ASP.Net MVC is by far the best ASP.Net solution MS has provided to date.

"In 2009, Microsoft released ASP.NET MVC, a thoroughly modern, orthogonal web framework supporting the most up-to-date understanding of how to architect well-factored, scalable web applications."<p>Astroturf should be left for the Jetson's dog to play on.