My previous article was a bit unstructured, so I probably have to make a nice little essay, which is more readable and has some examples, based on what i see around me, to make my point clearer and less rant like.
(It's not a rant on any person though)
Another note though that troubles me is that the design of many components is so restrictive, that it is hard to get around without looking at the source of eg the JTable to see what actually happens and why it eg resizes my columns when I don't want to (or not when I want them too). A lot of functionality is embedded in private methods, which normally just need changing, but instead you have to rewrite, or as often happens and probably not allowed, in copy & pasting over the original code to make happen what you want. I didn't hit that point yet in nyx, but when I do, it turning up to be a complete rewrite of swing I am afraid (to have those basic objects, that give me gui, instead of pretend model).
In short I want to know what happens without necesseraly hitting view source.
Another thing I forgot to mention is consistancy.
SWT lets you know that you have to get rid of everything yourself, so you know what you are up to (and save lot's of programming in the end). (some are a bit far fetched though). It is the exceptions that kill an application.
Swing leaves too much to be disposed, without people knowing it, which runs applications out of memory if that part of the application is used a lot.
Nyx gets rid of everything it creates, especially in swing. If a "leak" is left behind the only way to find is a profiler, which is a tedious task. So if you know of anything that doesn't get disposed correctly, mail it to me, so I can add it to nyx :)