ASP.NET compilation feature has made it faster. compilation itself means different today. making a text program into a DLL which is still a pseudo code how come saves time? it saves time exactly where? not while compiling im sure. not while reloading it in IIS. not while executing. hello?

Java binaries are byte-coded classes. The exactly same manner is what a ASP.NET DLL gets generated in. VB4 used to create pseudo code EXEs. all such pseudo code binaries get decompiled as easily. The overhead to actually run such a binary is similar to emulating. on a PC we don’t have a java hardware to run a class. a Virtual Machine is a emulator which pretents to know all the byte code instructions. Runs them in realtime converting each instruction to intel x86 assembly. Same goes with all vb4 or asp.net dlls. the overhead is real heavy. not noticing it does not make faster. faster is running those java games on mobiles! if you had the same clock x86 CPU running the same java game on the virtual machine, would be slower.
Ask game programmers. will they ever use GDI+ or DirectX from VB? ROFL! anyone who does game programming can tell that those programs have to render a entitre scene before the next a vertical retrace starts. that happens at least 50 times every second. They don’t want any middle men (or code for that matter) before their matrix reaches the hardware accelarator (video card). Using any class library would only add more functions to the stack between the actual thread and the hardware. Everything slowing down.

then comes the actual ASP.NET code between the RAW IIS HTTP Server and the actual ASP.NET thread. loads of functions, layers of classes, a entire tree of inheritance and the actual code in the end. All these layers are bound to include their overhead and will sure slow down the response time.

All said, how will you ever know what is the unit of this slow down. that sure is complicated to explain.