As with all IT surveys, enjoy with some salt... and let me give you my own take on Swing.
My company has been using Swing in production application use since 1999. For those of you who don't know, Swing is the cross platform GUI framework that has been part of the core Java platform releases since 1.2. It was available before Java 1.2 as a separate download - in fact, in the old days, we used to deploy the swing jar separately with our applications.
FMG's first GUI Java production applications were written using Java
AWT. Been there, done that, don't wanna go back! Swing was a breath of
fresh air, and we jumped on the opportunity to port our code from AWT to Swing.
I am frequently asked how Swing has treated us. It has been great. We have had ZAROO Swing related bugs since first rolling it out. The Swing based portions of our applications are pounded on daily by hundreds of end users. Millions of transactions have been put through these apps. And no problems. To top if off, I can run our apps on OS X, Linux, and Windows of all flavors.
We kept hearing in the IT press that "Java was dead on the desktop", that Swing had issues, and worse. Meanwhile, FMG was plugging away with one Swing based application after another. I never understood why popular opinion checked out hard on desktop Java for so many years.
HTML/HTTP is not adequate for all business applications - sometimes a user really needs a thick interface. (AJAX will have to be a topic some other day.) I think once Java became the de facto language of ecommerce - which was driven almost entirely from the server side - Java on the desktop became an afterthought for many. But Swing was always out there, and it was a solid way to get a business user a great thick GUI experience.
I read (and reread) .NET Framework Essentials when it first came out. I was amused (but not shocked) to see that Microsoft had in large part copied many of the best aspects of Java, and at many layers of the stack, from architecture all the way down to the syntax and grammar of the core language (C# to be specific). What really blew my mind was that they clearly based much of the design of Windows Forms on the Swing API's. If you knew Swing, Windows Forms was not going to be hard to learn.
Don't underestimate the import of Swing being one of the dominant GUI class libraries in use today. I think this is another sign that Java on the client is back on everyone's radar... and that rocks! Hats off to Sun and the Swing team for their much deserved success!