But it is quite different from web MVC that was popular with web frameworks like Struts.
I haven't looked at the more recent javascript frameworks, but my intuition tells me that they are probably going back to the original MVC pattern. (Observer pattern to notify views when model changes)
I've had as a low priority idea for a few years implementing a web MVC framework that is somewhat closer to the original inspiration - not because it makes sense for generating HTML (though it actually works quite well for that) - but because it would reduce the impedance mismatch with a client-side library using the original MVC pattern.
I have not actually done this for a number of reasons. The top one being that when you scratch an itch that you think someone else should have, it is much less fun and likely to work right than when you scratch your own itch. But it still bugs me that nobody has written one that works like I think it should...
As most developers in those days hadn't started with web apps it wasn't surprising that the term MVC was used - e.g. we were writing MVC C++ wrappers for simulations in 93/94 and Java MVC simulations in applets from '95.
But a 2000-2001 handrolled MVC framework does not qualify as "pre-Struts".
I was writing RDBMS in dBase, compiled with Clipper, on MS-DOS, in the early 1990's, when I was about 30 years of age. (I was the "old guy" 20 years ago)
Wow! The decades just keep passing by with increasing relevant speed.
I tell the younger guys that before IDE's and flat memory models were around, when you programmed, you went looking to buy three things.
1. Language/Compiler 2. Linker 3. Editor
And you will spend just as much time in the linker file (segmented memory back then) as you did coding.
The newer tools are just light years ahead of where they started back then. Its one area I will never look back at and wish it was still around.