5 ms·

For Java long start time is because it initializes big amount of RAM at the start, but thanks to this creating objects latter is fast. Additionally measuring of

For Java long start time is because it initializes big amount of RAM at the start, but thanks to this creating objects latter is fast. Additionally measuring of start of program is meaningless, what this say to us? Nothing. OK, maybe something, something like "write programs/scripts which execution is less than seconds in languages like ....". But for most of programs it doesn't matter. What the difference if program starts 3.1-3.2 seconds and 0.05 second? If execution time is longer than minute human will not see difference.

dchest 15y ago
For Java long start time is because it initializes big amount of RAM at the start. Why would this take so much time?
sheffield 15y ago
He wrote: "[...] it's pretty important when you are writing shell scripts / cron jobs / random commandline utilities.".
burgerbrain 15y ago
I can understand people decrying results of .05 seconds apart or so, but 3 second start ups? That would be infuriating. That kind of UX would take me back quite a few decades...
- kabdib 15y ago
  Garwk. I've helped write whole operating systems that boot in less time. [Atari ST. Check. Newton OS. Check. Other stuff I can't talk about: tens of milliseconds, mostly waiting for external crap like USB to initialize and settle down.]
- igouy 15y ago
  What przemelek actually suggested is that you won't notice the difference between a 63.1 second run time and a 60.05 second run time.
dougws 15y ago
I definitely notice the difference in speed between CLI utilities written in C and those in python or ruby.
jpr 15y ago
If xterm, less, ls, vi and others would take 3 seconds to start, I would never get anything done. I think it's sad that people think that 3 seconds is fast (unless the program is loading some big data of course).
- igouy 15y ago
  What przemelek actually suggested is that you won't notice the difference between a 63.1 second run time and a 60.05 second run time.

dchest 15y ago

For Java long start time is because it initializes big amount of RAM at the start. Why would this take so much time?

sheffield 15y ago

He wrote: "[...] it's pretty important when you are writing shell scripts / cron jobs / random commandline utilities.".

burgerbrain 15y ago

I can understand people decrying results of .05 seconds apart or so, but 3 second start ups? That would be infuriating. That kind of UX would take me back quite a few decades...

kabdib 15y ago
Garwk. I've helped write whole operating systems that boot in less time. [Atari ST. Check. Newton OS. Check. Other stuff I can't talk about: tens of milliseconds, mostly waiting for external crap like USB to initialize and settle down.]
igouy 15y ago
What przemelek actually suggested is that you won't notice the difference between a 63.1 second run time and a 60.05 second run time.

dougws 15y ago

I definitely notice the difference in speed between CLI utilities written in C and those in python or ruby.

jpr 15y ago

If xterm, less, ls, vi and others would take 3 seconds to start, I would never get anything done. I think it's sad that people think that 3 seconds is fast (unless the program is loading some big data of course).

igouy 15y ago
What przemelek actually suggested is that you won't notice the difference between a 63.1 second run time and a 60.05 second run time.