intel's Vanderpool and virtualization in general was Cell press release, redacted. 1672

Sander Vesik question.

for the mainframe batch system, there is a small matter that for 40 years (or more) that have evolved a "batch" paradigm where the responsible party for executing the program isn't present when the progeram is executing. as a result they have a long-standing default design point where the system needs to be doing things automagically on behalf of people that aren't present.

this continued with the batch-based "online" paradigm ... the responsible people for the deployed online application aren't present ... even tho the online application is providing various kinds of services for other individuals. the batch-based "online" paradigm has quite a large number of simularities with the client-server web paradigm .... where the sever side of the web paradigm is providing various kinds of online services for the client side users.

in contrast ... most of the recognized "easy to use" interactive systems have long standing design point that the person responsible for running the application is actually physically present when the application is run (aka rather than having extensive setup so the system can automagically handle various conditions ... it defaults to throwing it to the person that is presumed to be present, invoking the application).

many of the batch oriented systems have spent more than 40 years evolving their automagically handling methodologies.