Mark Thornton
Posts: 275
Nickname: mthornton
Registered: Oct, 2005
|
|
Re: Trip Report: Ad-Hoc Meeting on Threads in C++
|
Posted: Oct 20, 2006 9:42 AM
|
|
> It is true even today. Just look at Java IDE applications, > like NetBeans, Eclipse, JEdit... > > Why do you think a new Java Office would be any > different? > > The fundamental problem with Java is that it consumes "too > much" memory, and that inevitably slows down the system.
Those applications use a lot of memory by choice of the developers, not as a result of the language used. Simply they are keeping a lot of data in memory. If you give them the amount of memory their developers expect you to use, they perform pretty well. Some of Microsoft's recent applications have exactly the same problem for exactly the same reason. This is not to say that Java and similar langauges don't tend to use a bit more memory, they do, but in most cases the language itself accounts for only a small portion of the memory used. For an app like NetBeans which gobbles > 100MB on even small projects, less than 20MB of this could be attributed to the use of Java, and this amount is essentially constant (doesn't grow with bigger projects). These days 20MB is of little consequence in a desktop environment.
Over a decade ago, at an MS event, I heard one of their managers explain that you should target the amount of memory that will be typical on NEW machines at the time your product ships. Yes this means it might run like a dog on less well specified machines, BUT they weren't going to pay for your product any way.
|
|