SE vs. Light
Our firm has succesfully built and marketed a Java Application Platform, affectionately known as JAP.
It essentially consists of an app server, a common tool set and a build/continuous-integration environment.
All JAP applications must run in the app server, so obviously it is only for Java EE applications. But what about the rest - is there a market for a JAP SE?
At this point I am not thinking about the benefits or the implementation of JAP SE, I am just contemplating the name.
One name that has been tossed up there is JAP Light.
From a good neuro-linguistic-programming perspective, I am wondering if that is the best choice.
On the one hand, light is way more palatable than heavy – heavy baggage, heavy body – yuk! On the other hand, I would rather be considered a “heavy-weight” performer than a “light-weight”, and the package we are marketing includes performance!
So is it JAP Light or JAP SE or other (I mean, if Java EE had come first, would they have named Java SE as Java Light?)
It essentially consists of an app server, a common tool set and a build/continuous-integration environment.
All JAP applications must run in the app server, so obviously it is only for Java EE applications. But what about the rest - is there a market for a JAP SE?
At this point I am not thinking about the benefits or the implementation of JAP SE, I am just contemplating the name.
One name that has been tossed up there is JAP Light.
From a good neuro-linguistic-programming perspective, I am wondering if that is the best choice.
On the one hand, light is way more palatable than heavy – heavy baggage, heavy body – yuk! On the other hand, I would rather be considered a “heavy-weight” performer than a “light-weight”, and the package we are marketing includes performance!
So is it JAP Light or JAP SE or other (I mean, if Java EE had come first, would they have named Java SE as Java Light?)
posted by Victor Grazi at 2:00 PM
0 comments
