Java Desktop, taking back the power from the Web
This is not about Swing vs. SWT and this not about any L&F wars. In fact, I would love to have both UI toolkits work its best for whatever I'm going to use it for. I don't even care whether are more jobs for Java Swing developers than SWT either.
As we move forward, it's obvious that the advent of Rich Internet Application is not about Java anymore, in fact, in today's Web development the term "Pure Java" is dead and it is increasingly becomes boring as time goes by. From past experience, the only reason I saw Java being used as programming language for the web is that most Java programmers were too weak to code in Swing or SWT. But from where I learned my stuff, in this world, only Singapore is perfectly online to put so much love for anything Java and Web. In a bigger space, offline processes and asynchronous messaging is part of everyday business as what JMS and Middleware book authors has been emphasizing.
So why Java on the desktop? Ten years ago, the hardware can't catch up with the JVM and that was ten years ago. Today, why put everything in the server? And not exploit the power of the client? Deployment costs? Why not rethink your deployment strategies? The demand for offline processes is so huge that no one can ignore by now the efforts in developing Java desktop application in Swing or SWT, it already made perfect sense. Accept it or not, today the web belongs to Ruby.
There are instances where users can not be always online or even reliably online take for example, Third World rural banking where internet is still the future, business can not rely effectively on the web in this situation and definitely solutions providers who embraces Web already lost the opportunity to do business in this area.
Today and in the future anyone who wish to survive developing frontline applications in Java should start considering different desktop technologies that will help them switch and take back the desktop.
As we move forward, it's obvious that the advent of Rich Internet Application is not about Java anymore, in fact, in today's Web development the term "Pure Java" is dead and it is increasingly becomes boring as time goes by. From past experience, the only reason I saw Java being used as programming language for the web is that most Java programmers were too weak to code in Swing or SWT. But from where I learned my stuff, in this world, only Singapore is perfectly online to put so much love for anything Java and Web. In a bigger space, offline processes and asynchronous messaging is part of everyday business as what JMS and Middleware book authors has been emphasizing.
So why Java on the desktop? Ten years ago, the hardware can't catch up with the JVM and that was ten years ago. Today, why put everything in the server? And not exploit the power of the client? Deployment costs? Why not rethink your deployment strategies? The demand for offline processes is so huge that no one can ignore by now the efforts in developing Java desktop application in Swing or SWT, it already made perfect sense. Accept it or not, today the web belongs to Ruby.
There are instances where users can not be always online or even reliably online take for example, Third World rural banking where internet is still the future, business can not rely effectively on the web in this situation and definitely solutions providers who embraces Web already lost the opportunity to do business in this area.
Today and in the future anyone who wish to survive developing frontline applications in Java should start considering different desktop technologies that will help them switch and take back the desktop.
Comments