Don't get me wrong, I'm a big fan of MVC I just don't like posts like this. I feel like I should be going through each of your points and refuting it.
I'll hold myself back and just have a gentle dig at point #2.
2. MVC certainly isn't perfect control of urls. Sure it's a nicer default in most situations but it simply can't cover them all.
Taking your example of
http://localhost/Product/Detail/23213
That's not exactly a particularly user friendly url in my opinon.
Wouldn't the following be a much better url? (provided it's relevant to the page being displayed)
http://localhost/Computers/CPU/Intel/Intel-Xeon-3GHZ
Why are we still stronly coupling the url to the code it's running?
Just because the above url should use the product controller and another (http://localhost/Computers/CPU/Intel/) would use the category controller doesn't mean it needs to be specified in the url.
I'll hold myself back and just have a gentle dig at point #2.
2. MVC certainly isn't perfect control of urls. Sure it's a nicer default in most situations but it simply can't cover them all.
Taking your example of
http://localhost/Product/Detail/23213
That's not exactly a particularly user friendly url in my opinon.
Wouldn't the following be a much better url? (provided it's relevant to the page being displayed)
http://localhost/Computers/CPU/Intel/Intel-Xeon-3GHZ
Why are we still stronly coupling the url to the code it's running?
Just because the above url should use the product controller and another (http://localhost/Computers/CPU/Intel/) would use the category controller doesn't mean it needs to be specified in the url.
