Re: J2ME or network programming or...what do you recommend?

rasputin16002002@xxxxxxxxxxx wrote:
...
Now you are ready to learn more. I think J2EE is more popular than
J2ME, but J2ME tends to be more of a niche, and I would think less
competition for jobs too.

What do you mean by more?

Which of the three uses of more are you referring to?
The general answer is that 'more' means 'bigger than'
but its use might be modified by the context.
- 'learn more' already covered, but to quote Edison
"We don't know a millionth of one percent about anything"
- 'more popular' - I suspect Mark meant more work/more
projects, but also with more people vying for that work.
- 'more of a niche' - smaller (I would say much smaller)
market of work/projects & people going for them.

All that aside, I recommend going for one of the
'more popular' areas at this stage for a reason I
have not seen mentioned yet. The more popular
a technology is, the better help you are likely to
get on public forums, when striking difficulties.

For that reason, I think you should steer clear of
J2ME - it is not widely used.

OTOH - it pays to have a good grounding in J2SE
'desktop' before proceeding to J2EE 'server'.

Since you mentioned J2ME - which are apps. with a
rich client GUI, it makes me think that using the J2SE's
Swing GUI toolkit might be worth investigating.

The 'popularity' of desktop apps. to server side apps.
(about 1/20) suggests Swing rich client programming
would not be 'very popular' (it is possible to use a rich
client to connect to a web app. - but most web apps.
are designed to work in a plain old browser). But many
people have swung gradually from rich client GUI
development to thin client server-side development
(& can still remember Swing dev., and like to show
off their skill in it/keep their hand in).

--
Andrew Thompson
http://www.physci.org/

Message posted via http://www.javakb.com

.