Most webdev stuff that I've seen completely fuzzes the distinction between View and Controller, or changes it into something quite different from the original concept in MVC.

The original concept was never very clear, or at least never very clearly communicated.

I used to work downstairs from one of the UW CS&E faculty who helped push MVC, and I would disagree quite harshly.

The problem, such as it is, is that the original examples they tended to use involved systems where the View and Controller were physically separate systems. Consider a medical scan data viewer with (a) a screen (b) a series of controllers to manipulate what appears on the screen.

In this context, all 3 of MVC are clearly identifiable and easy to talk about and understand.

But as it got applied to GUIs where there are no distinct physical controllers and all the interaction occurs intimately tied to the View (i.e. what's on the screen), it is harder to find the boundaries between the V and C parts (and to some extent even the M).