much of suns emphasis lately has been on server-side and j2me technologies, and many industry pundits have predicted death knells for client-side java.
this makes some sense. lets look at some j2se facts:
the initial versions of java virtual machines (jvms) were bug-laden, slow, and unreliable, making it nearly impossible for the nascent java pioneers who had invested heavily in this technology to deliver a reliable, high-quality end-user experience. developers shied away from widespread adoption, despite rapid improvements to client-side java.
microsoft decided to exclude their version of java from windows xp, making client-side java even more difficult to deploy, and posing new headaches for client-side developers; for example, how will end users run my application if they first have to install java?
web services like sunone and .net requires abstraction layers and universal protocols such as soap and xml, and pushes most processing and logic to the server-side. this undermines the need for any client-side technology platform such as java, and provides the option to have all client-side applications delivered through a web... 下一页