Scalability Let's look at each of these in detail. A broad, consistent framework allows developers to write less, and reuse more. Less code is possible because the system provides a rich set of underlying functionality. A lot of programming infrastructure is either handled automatically by the CLR or rendered completely unnecessary. That is, some of it is hidden, and some of it is just not there any more.
Memory management is an example of hidden infrastructure.
Visual Basic developers stopped worrying too much about memory long ago. A simple declaration statement will do it, and the CLR allocates the memory as necessary. Then it goes on to handle reference counting on instantiations and automatically do garbage collection when the reference count gets to zero. Another example is proxies and stubs, which map interfaces on a remote object to the local system. The proxy handles communication with the remote object, and stands in its place locally, so that local processes can treat the remote object as if it were local, and the details of remote management are all handled behind the scenes.