I don't see the issue with calling it "ASP.NET MVC". The Visual Basic event-driven style of programming is fundamentally different from MVC. Calling it MVC provides context.
Would you have preferred they come up with a "cute" name that doesn't explain what it is?
I don't see the issue with calling it "ASP.NET MVC". The Visual Basic event-driven style of programming is fundamentally different from MVC. Calling it MVC provides context.
Would you have preferred they come up with a "cute" name that doesn't explain what it is?