CLDC, CDC, and J2SE Embedded

You may have seen the recent addition of J2SE Embedded to the J2SE website and asked yourself "What's the difference between J2ME CLDC, J2ME CDC, and J2SE Embedded? By now you probably know the difference between CLDC and CDC. CLDC is targetted towards small devices with limited resources, like cell phones. These devices have limited processing power, memory (minimum 160-512 KB memory), and limited displays. Many CLDC applications are written to the Mobile Information Device Profile, as MIDlets, which do not follow the "typical" J2SE type of programming model. CDC targets a larger device with more capabilities (2 MB of RAM and 2.5 MB of ROM), like newer smart phones and PDA's. Many CDC applications are written just like J2SE applications but with a subset of the API's available in J2SE. Both CLDC and CDC have optional packages which can be added to add additional capabilities not available in the core product. J2SE Embedded utilizes the full set of J2SE API's and therefore targets a device with more processing and memory (~13 MB) then either CLDC or CDC. Which one you choose depends on your needs and the capabilities of your target device. Whichever one you choose, there's a Java implementation to suit your requirements.

Comments:

An interesting thing to think about is that new Java programmers almost always learn on J2SE first before moving on to other editions of Java, like J2ME.

I think it is great that Sun is making J2SE Embedded available. It will allow more embedded developers to move onto the Java platform because they can actually start using it for embedded work while they are still learning the language.

Before J2SE Embedded, an embedded systems developer that wanted to start using Java in the embedded space would first have to learn Java on J2SE using examples and educational materials that were not related to embedded systems work. Then, the developer would have to go on to learn a smaller version of Java, like CLDC, before they could actually do embedded work.

J2SE Embedded should make a 2-step process a 1-step process and hopefully, over time, this will enable the pool of J2SE Embedded developers to grow large enough to start overflowing into the smaller versions of Java and increase the number of embedded developers working there to :-)

Posted by Ted Kosan on May 11, 2005 at 03:26 PM PDT #

I think, an implementation for even lesser memory is required to address programmable boards such as Arduino, Beaglebone, etc. Or, Espruino which is 'Javascript for Things' ! http://www.kickstarter.com/projects/48651611/espruino-javascript-for-things

Posted by Nagesh on October 05, 2013 at 04:27 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Darryl Mocek

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today