[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] Use of javax.* in new EE4J projects
|
You are definitely right that it is strongly associated with application servers and probably monolithic applications at large companies (where you have company tooling standards etc.). However, part of the perception of Java EE is probably generational. Someone who has a negative opinion of Java EE was probably using it 10+ years ago when Spring came along. My impression is that younger generations lack the J2EE biases, are ambivalent about Java EE, and lean towards Node.js/_javascript_. The older generation thinks an app container is heavy weight and prefer Tomcat whereas newer developers (last ten years) would skip Java altogether and go with Node.
I am concerned about loosing the Java EE brand recognition. My impressions (and from emails I received), Eclipse does have a negative reputation owing to the Eclipse IDE - even outside of the Java community.
I’d like to see someone with marketing experience involved with naming/branding. The EE4J community is a self-selected group which may not be representative of the larger community and specifically decision makers (like CIOs and middle managers).
I vote for keeping javax or something like javaee for the package names. A split personality in the platform sends the wrong message.
-Ryan
|
Attachment:
signature.asc
Description: Message signed with OpenPGP