Linked by Thom Holwerda on Thu 14th May 2009 15:39 UTC
Thread beginning with comment 363671
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Article in time,
by FunkyELF on Thu 14th May 2009 18:01
in reply to "RE[2]: Article in time,"
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 !
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 !
Look at Jython. They have an excellent tree example. I wrote jython viewer that connects to a database with hierarchical information in like 10 lines (clean and clear) of code. It just showed me the tree structure and printed information when you selected a node.
RE[3]: Article in time,
by marcelkoopman on Thu 14th May 2009 19:32
in reply to "RE[2]: Article in time,"
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 !
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.
RE[3]: Article in time,
by Bill Shooter of Bul on Thu 14th May 2009 20:17
in reply to "RE[2]: Article in time,"
There's no point going into a Java vs C++ argument here -- the question is one of toolkit design. Qt is an exceptionally well-designed toolkit (and has Java bindings, remember), but not everyone is fortunate enough to be in a position to use it, and in some situations it may not be appropriate.
Personally, I disliked the design of both the SWT and Swing toolkits when we studied them at university, but if I were required to write something using SWT, this article would be useful, so good job!
Now how about a series of articles comparing widget toolkits -- Qt, GTK, wxWidgets, FLTK, etc...?







Member since:
2007-03-23
But seeing that it deal with Java SWT, Beeuuuu :-*
I will implement it in Qt anyway, this night and in C++.
(maybe python who knows !)
So whats wrong with Java according to you?
Or you just want to show off that you can hack something in C++?