On C/C++ undefined behaviours (there is no "Eclipse")

[retard]

Sat, 02 Oct 2010 21:21:23 +0200, Don wrote:

> retard wrote:
>> Sat, 02 Oct 2010 18:21:53 +0200, Don wrote:
>>> There was just something sloppy in Eclipse's startup code.
>> 
>> I don't recommend running Eclipse on any machine with less than 1 GB of
>> RAM. It's a well known fact that Java programs require twice as much
>> memory due to garbage collection. Also Eclipse is a rather complex
>> framework. Luckily *all* systems, even the cheapest $100 netbooks have
>> 1 GB of RAM!
> 
> My laptop had 1GB, so I'm not sure we can blame that. Eclipse was
> perfectly fine once it had loaded. It was only the startup which was
> slow.

Another thing that comes to mind is that the file system might have been 
badly fragmented and/or Eclipse loaded a boatload of dependencies at 
startup from a slow 2.5" disk.

Many laptops have slow 5400 rpm disks with really bad I/O performance. 
For example my old IBM T23 or something like that managed to read files @ 
8 MB/s from the C: drive. That's just terrible compared to modern SATA2 
hard drives with 64 MB of cache (SSDs are even better -- a 64 GB 2.5" SSD 
drive costs about as much as a 3.5" SATA2 1.5 TB spinning disk). I can 
easily read data @ 90 MB/s, even when the file system is quite full. If 
you need to read 120 MB of data (size of the latest eclipse), there is 
simply no way to read it faster than in 15 seconds using the old disk.