But I think Java's age is showing, and its not well suited for use on AMD's new 16 core CPU.
Henry Wong wrote:What makes this processor bad for Java?
But its just too hard (IMHO, YMMV) to manually decompose your application, fix the race conditions, etc. When commodity computers have lots of cores, mainstream developers are going to need the language/compiler/runtime system to do it for them. Its already clear with the common quad processors, going to 16 is just going to make it worse.
I don't know what the future answer will be, as writing correct parallel programs is really, really hard. But I don't see Java as the tool to do that. Perhaps Scala, perhaps something completely new.
Pat Farrell wrote:
Henry Wong wrote:What makes this processor bad for Java?
Its not this particular processor that is bad for Java. Its Java is bad for that processor. Or, rather its that while Java has Threads, (see Henry's excellent book), its too hard.
When we had single processors, it was OK to use threads manually to allow for responsive GUI, etc.
But its just too hard (IMHO, YMMV) to manually decompose your application, fix the race conditions, etc. When commodity computers have lots of cores, mainstream developers are going to need the language/compiler/runtime system to do it for them. Its already clear with the common quad processors, going to 16 is just going to make it worse.
I don't know what the future answer will be, as writing correct parallel programs is really, really hard. But I don't see Java as the tool to do that. Perhaps Scala, perhaps something completely new.
SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
Rob Prime wrote:By the way, you say that writing parallel programs is hard in Java, but with java.util.concurrent, java.util.concurrent.atomic, the executor framework and inclusion of SwingWorker it's never been easier writing parallel programs in Java.
All desirable things in life are either illegal, banned, expensive or married to someone else !!!
Bear Bibeault wrote:What do you see as the compelling alternative?
Praful Thakare wrote:Also what does IMHO and YMMV stands for ?
Praful Thakare wrote:Application servers and frameworks (or technologies) like ejb is better
Pat Farrell wrote:Other than folks supporting legacy implementations.
Paul Clapham wrote:And this is why I answered "yes". Millions of lines of Java code have been written and even if people stopped writing Java tomorrow -- which they won't -- there would still be the need to support that code for years to come.
Anila Mathew wrote:any other programming language in future... will have the flexibilty and ease of learning like Java.
Google or urban dictionary, or hacker's dictionary will define it for you. Better than us just telling you.
[My Blog]
All roads lead to JavaRanch
Anila Mathew wrote:
I hope whatever comes new , will have the flexibilty and ease of learning like Java.
No more Blub for me, thank you, Vicar.
"Half of the science is to ask question"
Arun Kumar wrote:
If a language has to stay it shoudl have some qualities which are better than others
Arun Kumar wrote:
If a language has to stay it shoudl have some qualities which are better than others...
No more Blub for me, thank you, Vicar.
There are only two kinds of languages: the ones people complain about and the ones nobody uses.
chris webster wrote:
Java will last as long as there are enough people who feel it is "better" for what they want to do with it. Then it will be replaced by something, well, "better"!
SCJP 1.4, SCWCD, SCDJWS
Henry Wong wrote:This was quoted during the period where C++ was poised to become the premier object oriented language.
Will Lee wrote:How about follow Microsoft's step: make your project (which is Java in this case) hostile to your competitor? Then the industry will drift away from this language.
Maybe it's time to join .NET?
![]()
Will Lee wrote:
How about follow Microsoft's step: make your project (which is Java in this case) hostile to your competitor? Then the industry will drift away from this language. Perhaps nobody is going to complain about Java anymore at that time .
No more Blub for me, thank you, Vicar.
Paul Clapham wrote:that none ... even mention Java. They are all talking about databases, and servers, and virtualization,
Will Lee wrote:I can't help wondering, can I still code in Java in 10 (or 5) years?
![]()
![]()
SCJA
~Currently preparing for SCJP6
Brian Legg wrote:
My only complaint with Java.... I can't find any workI've been doing MS crap for so long now and I hate it... I miss doing Java professionally.
![]()
Will Lee wrote:I can't help wondering, can I still code in Java in 10 (or 5) years?
![]()
![]()
Dont worry, with MS coming up with new versions of its own languages every year, you will soon be forced to switched to java
Henry Wong wrote:. Why would anyone go out of their way to restrict themselves? It may be comfortable. And hence, it may be enjoyable. But heck, isn't trying out and learning new stuff enjoyable too?
Paul Sturrock wrote:
Dont worry, with MS coming up with new versions of its own languages every year, you will soon be forced to switched to java
Doesn't Sun release new version of Java every year?