Posted: Feb 5, 2007 10:21 AM
> First, the whole examples are meaningless, since we're
> talking about Swing and not the Java language.
Sorry, but you're wrong. I was responding to a post that claimed that MS get's to do "do-overs", but Sun doesn't. Swing had nothing to do with the comparison.
> did really have problems in its early life, the Java
> language works very well. For instance, a lot of people do
> appreciate checked exceptions and so on.
I was just illustrating Sun's reluctance to change some of their more dubious decisions even when there's a lot of community interest in doing so. I'd be surprised to find many Java programmers who think Sun made the best decisions on all the items on my list.
Coming back in
> topic, for what concerns Swing Sun has _already_ performed
> some do over, and in fact Swing is today perfectly usable
> in areas, such as native l&f rendering and performance.
OK, let's talk about Swing then. Just about everything I've read about multi-threaded programming says that it's often useful, but that you should avoid it if it really isn't necessary. The design of Swing forces you into multi-threading even when there's really no good reason for it. Has this been changed?
The point is that although Sun does adds functionality to Java and works to improve performance, it really doesn't go back and rework the fundamentals even when there are flaws.
Again, they may have their reasons, but they aren't being treated more harshly than any other vendor.