In additional to personal preferences, cultural predispositions too play a role in this particular decision process.
A lot have been written about Japanese auto manufacturers continuing to reduce engineering tolerances even in the absence of externally enforced market demands. This has often been contrasted with the American auto manufacturer's purported management style where they would only meet the level of tolerance necessary (for assembly and finished product quality) but no more. Anything more was perceived as wasteful and misallocation of resources. I do not know how much truth is there to those stories.
I guess the answer depends on where in the spectrum of business vs pleasure does the act of coding lie. Even for business software, it hardly ever lies in the "purely business" extreme. Or so I would like to think. Inefficencies like that bother the hell out of me, and will nag me no end.
Many live with Eclipse regardless of its startup time.
I'm reminded of the (probably apocryphal) story of how IBM did a trial outsourcing of some electronics manufacturing to Japan, back in the 50s or 60s when this was considered risky. Their contract specified a 3% defect rate, which was considered very low at the time.
Months pass and IBM gets their order delivered in big crates. They pop one open and find that some of the parts are stored in a bag at the top. There is a note attached, which reads: "We do not understand why you desire 3% faulty parts, but for your convenience, we have packaged them separately."
I presume "engineering tolerance" means increased quality over time?
Inefficiencies like that bother the hell out of me, and will nag me no end.
Right on! I wish hollywood have that kind of attitude toward inefficiency too. It's quite maddeningly to me the way they think. I just can't understand them.
A lot have been written about Japanese auto manufacturers continuing to reduce engineering tolerances even in the absence of externally enforced market demands. This has often been contrasted with the American auto manufacturer's purported management style where they would only meet the level of tolerance necessary (for assembly and finished product quality) but no more. Anything more was perceived as wasteful and misallocation of resources. I do not know how much truth is there to those stories.
I guess the answer depends on where in the spectrum of business vs pleasure does the act of coding lie. Even for business software, it hardly ever lies in the "purely business" extreme. Or so I would like to think. Inefficencies like that bother the hell out of me, and will nag me no end.
Many live with Eclipse regardless of its startup time.