Linked by Thom Holwerda on Mon 22nd Oct 2007 21:23 UTC
Java Sun's starting to phase out mobile Java that's been the standard on cellphones and other small devices in favor of their standard edition, which are made for PCs everywhere. Sun VP James Gosling's reasoning for shifting everyone over to Java Standard Edition is because 'cellphones and TV set-top boxes are growing up', meaning they're getting enough processing power to handle all the demands of full-featured Java.
Thread beginning with comment 280035
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Why different version afterall
by Matzon on Tue 23rd Oct 2007 04:59 UTC in reply to "Why different version afterall"
Matzon
Member since:
2005-07-06

I like the fact that there is a jre and then different sdks. The J2EE package contains a lot of stuff that is irrelevant for J2SE.
The reason why .net doesn't even have a EE edition, is because they don't have anything enterprisey ;)
The sheer number of enterprise solutions and packages (3rd party, jsr's etc.) is waaaaay higher and more advanced than .net. Not becuase .net is necessarily inferior, but simply because of java dominating in this marketspace (unlike desktop).

Reply Parent Score: 7

google_ninja Member since:
2006-02-05

I don't know how true that is. The more popular frameworks have already been ported over (hibernate, spring), and I find that The .net Way scales up a hell of alot better then The Sun Way scales down. I would still recommend J2EE for the largest of projects, but that really doesn't cover a huge amount of stuff. The problem with J2EE is that it is far too over engineered, and you and to do ANYTHING you have to write a ton of "plumbing" code. Once you have that done, it tends to work very well, but from a purely development point of view, I am a hell of alot more happy working with .net.

DISCLAIMER: I havnt really done J2EE work for about 4 years now, although before that it is all I did for about 3 1/2 years. So if something changed recently, I wouldnt know.

Reply Parent Score: 2

Matzon Member since:
2005-07-06

J2EE has changed A LOT - most of the plumbing code is now auto generated (for better or worse).

EJB3 has really made a lot of differences and stuff like JPA which integrates nicely with netbeans is really really nice.

However J2EE is really an abused term, since it covers a ton of technology, some better documented and used than others.

Reply Parent Score: 2

snozzberry Member since:
2005-11-14

DISCLAIMER: I havnt really done J2EE work for about 4 years now, although before that it is all I did for about 3 1/2 years. So if something changed recently, I wouldnt know.

I'm offended that you qualified criticism with intelligent caveats based on your actual knowledge. You're holding the rest of us to an unreasonable standard.

Reply Parent Score: 3

bariole Member since:
2007-04-17

1) .Net versions of Spring and Hibernate are not as good as Java ones. In spite of that I doubt that these days there is a greate difference (from develeoper's point of view) between .net and j2ee for small to medium sized projects.

2) Thanks to Spring plumbing is gone now. Present problem with modern j2ee are view technologies and the whole "threat browser as app enviroment" aproach. JSP and others tend to be a major pain in the ass when compared to something elegant and proper (WinForms for example). Hopefully Flex or JavaFX will take care of that.

Edited 2007-10-23 19:04

Reply Parent Score: 1