Response.Write("I'm an OO method")
The first time I saw that, I thought, "oh shit. They borrowed the Java anti-Demeter dot bloat for print()".
VBScript is brain dead when it comes to constructing objects, but you ain't gonna get very far with ASP without objects.
Do you mean that one has to use existing OOP API's in order to talk to MS services, or that one must create their *own* classes in order to implement maintainable biz logic?
and my guess is that had a lot of "objective" reasons why they chose the path they chose.
Microsoft objective? Ha ha. Actually, they tend to copy what a competitor is selling well at a given time. MS is not known to love OO. They were slow to fix the inheritance in VB, for example.