Blogs by topic Deployment and user javakiddy
| • Accessibility | • Ajax | • Blogging | • Business | • Community |
| • Databases | • Deployment | • Distributed | • Eclipse | • Education |
| • EJB | • Extreme Programming | • Games | • GlassFish | • Grid |
| • GUI | • IDE | • Instant Messaging | • J2EE | • J2ME |
| • J2SE | • Jakarta | • JavaFX | • JavaOne | • Jini |
| • JSP | • JSR | • JXTA | • LDAP | • Linux |
| • Mobility | • NetBeans | • Open Source | • OpenSolaris | • OSGi |
| • P2P | • Patterns | • Performance | • Porting | • Programming |
| • Research | • RMI | • RSS Feeds | • Search | • Security |
| • Servlets | • Struts | • Swing | • Testing | • Tools |
| • Virtual Machine | • Web Applications | • Web Design | • Web Development Tools | • Web Services and XML |
Deployment
When will Java applications 'just work' out-of-the-box on the desktop? I have projects crying out to be written in Java, so why do I find myself considering other technologies? Is "Java" really a dirty word on the desktop?
Why do so many people think the JRE download size is a problem? What causes the end user to readily download one plugin, while ignoring another? Is it just a numbers game? It's time to engage in a spot of amateur Psychology...
I've spent a fair amount of time over the last few years writing Java desktop applications, and I've quite a collection of scars to prove it. I know Sun are looking to improve SE JRE deployment in upcoming releases, so here's a few uneducated ramblings to add into the ideas pot. :)
