I guess Microsoft conspired to put all those design flaws and bugs in
the JDK too:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
To aid any developers wondering what's going on with the JDK and
JFC/Swing I would just like to point to JavaSoft's BugParade search
engine.
Searching on April 3rd with this criteria:
+1.1.6 - 705 bugids
+1.1.6 +"In progress" - 199 bugids
+1.1.7 - 64 bugids
+1.2beta4 - 281 bugids
+swing1.0fcs - 495 bugids
+swing1.0fcs +"In progress" - 135 bugids
+swing1.1 - 55 bugids
+1.1 +"In progress" - 1424 bugids
I found annoying things in there, like fixes to JDK1.1 which
only will be atttributed to JDK1.2 ie. never fixed in JDK1.1
(bug ex: 4082050), new bugs that break previous bugfixes, API changes
(bug ex: 4108756), workaround suggestions that are unstable, and
priority given to simple stuff and licensees rather than the ones a
lot of people really want according to the Top 25 bugs (e.g: 4065018,
4085578, 4079333).
I have faith in the team, but I doubt that we'll see a truely stable
JDK untill late this year, and developers should be aware of any
showstoppers. I sometimes question their priorities when I hear about
the new APIs and products, but then again, I didn't pay anything for
this software.
It would be taking a cheap shot to compare the JDK situation with
other products and companies, however we are at the mercy of JavaSoft
to fix their ("our") bugs. It's easy to say "we told you so", but
people have become so used to using incomplete software these days
(like certain operating systems) that JavaSoft should take even more
responsibility for their success. Attention spans are decreasing by every new press release.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> |
