Jeffrey I Condon/Cupertino/IBM wrote:
>
> A proposal for fixing the Java programming language's threading problems
> -------------------------------------------------------------------------
> Allen Holub suggests that the Java programming language's threading model
> is possibly the weakest part of the language. This article proposes
> significant changes and additions to the Java language that would address
> many of these problems.
> http://www-4.ibm.com/software/developer/library/j-king.html?open&l=258,t=gr,p=j.king
>
> Get a Free CD full of Linux/Java e-business solutions from developerWorks
> -------------------------------------------------------------------------
> Build open, integrated XML, Java and Linux e-business solutions using this
> free Developer
> Toolbox CD Set. Order yours today.
> Submit CD Request
> http://www.alphaworks/aw.nsf/html/DevToolsCD?open&l=jlbd,t=gr,p=j.jLog
>
> Reassigning object reference of a locked object
> -------------------------------------------------------------------------
> Peter Haggar warns us of the unexpected results when we reassign the object
> reference of a locked object without meaning to.
>
>http://www-4.ibm.com/software/developer/library/praxis/pr56.html?open&l=258,t=gr,p=j.locl
>
I agree with the author that threads in Java are presented in a way that
encourages developers to use them incorrectly. Threads in Java are
currently only useful for very trivial applications (like animation,
etc). In these types of applications, threads are only minimally
useful.
The real power of multi-threaded programming is that it allows an
application to scale (i.e. spread load across multiple processors.)
Java is really good at giving multitudes of novice developers the
mistaken idea that Java magically fixes all of the low level concurrency
issues and that their Java application will run faster because it is
"multi-threaded". When it does not, they blame the VM or the underlying
OS which is going through hell to make up for a poorly written
application. For the experienced developers Java threads are not
flexible enough to support the additional complexities of writing a
cooperative (scalable) application.
I would venture that without some sort of change in Java threads, or at
least a change in the thinking of Java developers, it will be impossible
to write JVMs that will offer satisfactory scalability.
Finally, [EMAIL PROTECTED], you need get involved in the Java
Community Process (JCP). Don't just talk about it, do something about
it. Submit a JSR. I think that IBM is a member of the JCP executive
committee so, if the JCP works, some of your changes could easily be
pushed into reality.
Matt Peterson
Caldera Systems, Inc
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
