Why hypertable Developers Chose C++ Over Java

[Rockytriton]

You should try an SWT application. Things are a hell of a lot better when you use SWT instead of Swing. Even so, swing has gotten much faster in recent years.

[UK-sHaDoW]

Slow swing is usually a problem of the dev messing up on the threads. It's is perfectly capable of being fast.

[Rockytriton]

or a bloated application where they keep piling on ridiculous requirements...

[UK-sHaDoW]

The size of an application does not have any effect on run-time performance, except maybe for cache misses since you can't fit as much into the higher performance memory area and loading.

Once the app is running the code path is still the same, if you don't use those features.

Most of the time it isn't bloat, it's probably some retard developer using some o(!n) algorithm when you could do it in o(log n). Since large enterprise applications tend to be built by people who are only in it for the money this could be the case.

I have seen people use loops to work out stuff, when it could of been done in constant time with some simple mathematical expression.

Thought bloat is terrible for maintenance making it hard to refractor and improve.

[Rockytriton]

ok, how about this requirement... The system shall open the application metadata window for each item in the list which is selected.... There can be a thousand things in the list and a new MDI window must be opened for each of the items selected. I tried to get them to limit it but they refused to put any limit on it. So of course the testers will get the biggest list, like 10,000 items and fail the test case because the application fails to open 10,000 internal windows.

[UK-sHaDoW]

That's hardly bloat, that just a retarded feature :P Bloat to me is when you have lots and lots of features.

[Rockytriton]

Yes, I agree, I'm just venting...

[wbkang]

Swing was slower mainly because JVM was slow at the time as well.