I'd like to design some software in java and have it work, without any headaches, on a portable device (I'm envisioning a palm pilot, Ipod, Cell phone,. the playstation thing . . or something similar)
I can't seem to find a list of devices which take bytecode. I imagine I would be doing mostly text based stuff.
--
"When you have to choose between a first-rate company with a
second-rate product and a second-rate company with a first-rate
Sun used to make a Java chip. I don't know what happened to that.
Generally your write a Java interpreter or a Just-In-Time Compiler for the platform you are running on. For smaller, embedded platforms you might want to look into J2ME.
Sun used to make a Java chip. I don't know what happened to that.
Generally your write a Java interpreter or a Just-In-Time Compiler for the platform you are running on. For smaller, embedded platforms you might want to look into J2ME.
Sun used to make a Java chip. I don't know what happened to that.
Generally your write a Java interpreter or a Just-In-Time Compiler for the platform you are running on. For smaller, embedded platforms you might want to look into J2ME.
Have you looked at some of the Blackberry devices? e.g.
formatting link
It appears that development for this device is primarily Java based. There is developer info on their website - It looks comprehensive, although I haven't used it.
If you find a list of Java enabled devices, then post back and let us know. However, I think it might be a case of trawling each manufacturer's web site, or maybe post your question on a handhelds newsgroup, if such a thing exists - I would guess it does.
I'm curious, does anybody know how much additional cost overhead is involved with this combination (Jazelle and a Java co-processor) over a comparable PIC or Atmel AVR processor, which wasn't designed to work with Java?
A friend of mine is a desktop developer and often argues that development time is dramatically reduced by programming in interpreted languages, such as Java because developers don't have to worry about memory leaks, buffer overflows, etc. In the embedded systems world, however, I can easily fathom a situation where cost of manufacturing would eventually outweigh the costs saved by programming in Java.
For example, let's say that it costs a company $20,000 to develop the software for some embedded system project in Java and $100 per device to manufacture this product with some kind of Java co-processor included. If we were to sell 20,000 units in the first year, we would be up to $2,020,000 in costs, which includes the cost of developing the software and manufacturing of each device. Now lets say that it takes double the money to develop the code for the same product in a combination of C and Assembly. So that's $40,000 to develop the code; but, we no longer require the Java co-processor, so our product (in this fictional example) costs only $50 to manufacture each unit. Again, we sell 20,000 units of our product. In this example, our overhead for the first year is $1,040,000, which is a little more than half that of the original product that we developed in Java.
I'm not trying to start a language war here or anything. I would just like to know how close to a real world situation my example actually is.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.