Linked by Thom Holwerda on Thu 14th May 2009 15:39 UTC
Java This article explains how to develop and implement trees in the Standard Widget Toolkit. Learn how an SWT tree is created and populated with data, how columns can be used to categorize data, how a tree can be extended to support row sorting, and how the tree's content can be searched.
Thread beginning with comment 363689
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Article in time,
by marcelkoopman on Thu 14th May 2009 19:32 UTC in reply to "RE[2]: Article in time,"
marcelkoopman
Member since:
2007-03-23

show what ?

Anyway, I don't like Java and its speed disaster.
Some years I heard about an OS written in Java, still alive ? XD

C++ is for robust things, Python is for prototyping this is the best combination !

Speed disaster? Come on, please be correct. Java was slow in the beginning of its release. Current JIT compilers are as fast as C++ / native code or even faster in some cases.
Why do you think NASA is using Java instead of C++? Because of pointer bugs. Its not reliable enough.

Reply Parent Score: 0

RE[4]: Article in time,
by boulabiar on Thu 14th May 2009 21:24 in reply to "RE[3]: Article in time,"
boulabiar Member since:
2009-04-18

[q]show what ?
Speed disaster? Come on, please be correct. Java was slow in the beginning of its release. Current JIT compilers are as fast as C++ / native code or even faster in some cases.[q]


So that's why OpenOffice is too fast, and Eclipse is too fast, and netbeans is too fast and JavaEE apps are tooooooooo fast

Reply Parent Score: 1

RE[5]: Article in time,
by Matzon on Thu 14th May 2009 22:14 in reply to "RE[4]: Article in time,"
Matzon Member since:
2005-07-06

dude, OOo is C++!

You are mentioning HIGHLY complex and dynamic applications. QT Creator doesn't even skim the surface of the capabilities of Eclipse & Netbeans.

Stop trolling and get back into your cave, you've obviously been sleeping in it for the last 5 years.

Reply Parent Score: 2

RE[5]: Article in time,
by Savior on Fri 15th May 2009 00:45 in reply to "RE[4]: Article in time,"
Savior Member since:
2006-09-02

Except OpenOffice is written in C++ ;) And Eclipse was waaay faster than KDevelop when I last checked it...

Reply Parent Score: 1

RE[5]: Article in time,
by pmarin on Fri 15th May 2009 07:01 in reply to "RE[4]: Article in time,"
pmarin Member since:
2006-12-30

Probably your computer is toooooooo fast also ;)

Reply Parent Score: 1

RE[4]: Article in time,
by adkilla on Fri 15th May 2009 09:44 in reply to "RE[3]: Article in time,"
adkilla Member since:
2005-07-07

The major problem with Java/.Net (or most VMs for that matter) is not its speed, but rather the high memory requirements for initial JIT compiling of bytcodes whenever they are loaded and the GC tuning that is required to develop performance apps with it. A way around the JIT memory requirement is to do AOT. This would however not solve the GC problem and make your Java app non WORA.

The J2ME JVMs tend to interpret code when there isn't enough RAM to JIT compile classes. Some J2ME VMs, like the IBM J9, can accept AOT compiled classes that do not have the JIT overheads, but would only run on CPUs they were targeted for.

-Ad

Reply Parent Score: 1

RE[4]: Article in time,
by l3v1 on Mon 18th May 2009 12:29 in reply to "RE[3]: Article in time,"
l3v1 Member since:
2005-07-06

Current JIT compilers are as fast as C++ / native code or even faster in some cases.


So that's why I hear chantings and chorus performances and whole concertos about JNI in the back of my head whenever I need to code a cpu-hungry algorithm.

Reply Parent Score: 2