By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,952 Members | 1,384 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,952 IT Pros & Developers. It's quick & easy.

"Java everywhere" is for world domination - Server-side work is passe!

P: n/a
asj
luke: BORRRRRRRRING......the most interesting initiatives are
happening on the client side - in small wireless devices such as
cellphones and smartphones, where J2ME has become the de facto
standard for application development.

Article from Javaworld.com:
"Java everywhere is for world domination"
http://www.javaworld.com/javaworld/j...wireless.html?

Some quotes:

- As smart wireless device shipment far exceeds PC shipment this year,
the Windows PC is no longer the de facto client platform. In a keynote
speech delivered to Microsoft developers in March 2003, Bill Gates
likened today's wireless market to the "early days of Windows," where
there are huge opportunities for profits and new jobs, and no dominant
player. The opportunity for Java to become a truly ubiquitous
end-to-end platform has finally come.

- What is "Java everywhere"? In technical terms, "Java everywhere" is
a single-architecture, end-to-end solution. The Java platforms on the
server side (Java 2 Platform, Enterprise Edition, or J2EE), client
side (Java 2 Platform, Standard Edition and Micro Edition, or J2SE and
J2ME), and inside embedded devices (J2ME and JavaCard) share the same
basic language features, API designs, libraries, and even development
tools. The value proposition of "Java everywhere" for developers is to
maximize productivity and allow existing developers to enter emerging
markets without extensive retraining.

- As announced at JavaOne, Java runtimes are built into more than 150
devices from more than 20 manufactures. All five major cell phone
manufactures have committed to the Java platform. In addition to
manufacturer support, Java has also gained widespread support from the
wireless carrier community.

- A major effort has been made to support games on J2ME handsets.
Mobile entertainment has proven to be an extremely profitable sector.
In Europe, simple ring-tone download has generated $1.4 billon in
revenue last year. In comparison, the entire global J2EE server market
is $2.25 billion. J2ME games are content rich, over-the-air
downloadable, and micro-payment-enabled. The J2ME gaming sector is
projected to grow explosively and create many new Java jobs in the
next couple of years. In fact, J2ME games are already the second
largest revenue source for Vodafone's content service.
ll*****@yahoo.com (luke) wrote in message news:<58**************************@posting.google. com>...
PC magazine tested five Java (J2EE) app servers (Websphere, BEA
Weblogic, SunONE, Oracle and the open source JBOSS) as well as
Microsoft's .NET (using Windows 2003 Server).

BEA's J2EE appserver Weblogic was the number one choice
IBM's J2EE appserver Websphere was the close second choice.
JBOSS trailed the pack, with Oracle, .NET, Sun making up the middle.

There's also a case study why a shop chose IBM's Websphere over .NET
and others (runs on Linux, etc).

Some comments:

- Choosing Microsoft means giving up cross-vendor compatibility, and
you'll have to forget about running servers on Linux.

- Unlike solutions from BEA and IBM, .NET doesn't offer the
reliability and security needed for enterprise Web service deployment

- The .NET path offers fewer options in building business logic and
database components. Microsoft has no official blueprint for business
objects comparable to Enterprise JavaBeans (EJB), though it recommends
best practices on the Web (www .microsoft.com/resources/practices).
The .NET developers have to devise their own component models based on
these practices, while a J2EE developer just needs to run a wizard to
get EJB.

- While it is easier to field a .NET solution quickly, the rigidity of
the EJB specification ensures that large-scale development projects
can enforce best coding practices and design rules. But this
stringency comes at the cost of more difficulty for the average
developer to master. .NET makes development and deployment very easy,
yet it requires extensive customization if you want to build a
mission-critical environment in which reliability, transaction
integrity, and message queue management are essential.

- If your company chooses to develop mission-critical applications in
.NET, you'll find yourself at Microsoft's mercy regarding upgrades,
licenses, and support.

http://www.pcmag.com/article2/0,4149,1218682,00.asp

Jul 19 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.