i know this has been beaten up one side and down the other, but is swing really all that bad ? also, is it a dying framework ? it seems swing is a rare requirement in job listings im browsing. J2EE is the big are in demand. I guess its not suprising, as a former VB programmer, ive witnessed the transition in demand to server side development with ASP, and now with dotnet. Just wondering what everyones thoughts are regarding the future of Swing as a framework.
"The Rebel army is now the legitimate property of the Army of the Potomac." - Joseph Hooker spoke these pompous words shortly before he was soundly defeated by Robert E. Lee at Chancellorsville
There are some UIs that just can't be nicely done in HTML, and thus there's still a need for a Swing API or its ilk. That demand for server-side programming has increased doesn't mean that the need for UIs has really gone away. Note that the Eclipse project did develop an alternative GUI class framework, the Standard Widget Toolkit (SWT). Has anyone here used the SWT to be able to speak to how it compares to Swing and AWT?
Sun and Java have definitely proved themselves in the server-side market, thats why J2EE and RMI are such hot architectures. Java still leaves a bit to be desired on the front end segment, but Swing isn't all that bad. I think light weight components have been overly beaten up for being slow. The strong MCV architecture behind them more than makes up for the that when it comes to making customized/customizable data models and representations. I believe Swing is still in the market. It probably just needs a little understanding of fine tuning for performance and some better marketing!