On 9/28/2010 7:27 AM, Ricky Clarkson wrote:
A language that makes it harder to build up large broken codebases is
needed. E.g., in Swing, it's really hard to unpick an evolved large
program that does concurrency wrong without breaking bits, whereas
.NET throws an exception if you instantiate a component on the wrong
thread, making that particular screwup impossible (unless you never
test the code and just keep growing it instead).
This is a truly silly issue with Swing. The Swing team has argued in
forums, BOFs, etc, that one should use AOP or other approaches to add
assertions to Swing that things are done on the appropriate thread.
That's a royal cop out. No one other than the Swing team truly knows
precisely which things must always be done on a particular thread -- and
it therefore *must* be their job to add appropriate assertions to this
effect. I understand Sun was in a financial bind for the last few years
-- that would have been an honest answer to the plea for such assertions
in Swing. It clearly must be done and must be done by the Swing team,
though.
--
Jess Holle
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
