> Well, most higher level languages are getting interpreted, which require some cpu time to startup. Even with something not-so-high-level-but-sorta-high-level like Java or C#, you still have an abstraction level (JVM/CLR) that must first boot, then interpret, then execute.
Startup times of typical VMs on modern hardware are mostly insignificant compared to initializations of various libraries and frameworks inside the actual application (and in many GUI applications there is outright call to sleep() in initialization code).
On the other hand this seems somewhat inconsistent with the fourth point. For example GIMP plugins are external processes and most of the (long) startup time of GIMP is spent exec'ing random small binaries that output few bytes of data and then exit.
Startup times of typical VMs on modern hardware are mostly insignificant compared to initializations of various libraries and frameworks inside the actual application (and in many GUI applications there is outright call to sleep() in initialization code).
On the other hand this seems somewhat inconsistent with the fourth point. For example GIMP plugins are external processes and most of the (long) startup time of GIMP is spent exec'ing random small binaries that output few bytes of data and then exit.