Linked by Thom Holwerda on Mon 22nd Oct 2007 21:23 UTC
Java Sun's starting to phase out mobile Java that's been the standard on cellphones and other small devices in favor of their standard edition, which are made for PCs everywhere. Sun VP James Gosling's reasoning for shifting everyone over to Java Standard Edition is because 'cellphones and TV set-top boxes are growing up', meaning they're getting enough processing power to handle all the demands of full-featured Java.
Thread beginning with comment 280095
To read all comments associated with this story, please click here.
by chrish on Tue 23rd Oct 2007 12:39 UTC
Member since:

Who, exactly, thought that Java on embedded systems was a good idea? No CPU cycles to spare, very little RAM, slow storage, etc. It takes my phone ages to load a Java app, and it's completely useless while Java is loading.

I'm reasonably certain that my Nintendo DS has a lot more power/RAM than my cell phone, but I wouldn't run Java there.

That said, I do use Eclipse sometimes on my iBook, which is certainly painful.

- chrish

Reply Score: 4

RE: argh
by sanctus on Tue 23rd Oct 2007 13:16 in reply to "argh"
sanctus Member since:

when I switch back from Ubuntu to OSX this weekend, I tried to find a equivalent to the IDE a was using with gnome.

My requirement are code completion, macros, regex, color syntax

I tried all the python/wxpython ide/text editor I know. (spe, drpython, edittra, PyPE, ulipad). wxpython is a hell slow on OSX, plus it has many interface glitch. Code completion took eternity to show up choices, far more than to write it. Simple scrolling of text use up to 80% cpu.

I finally stop and fully use eclipse which was the lightest and fastest of all IDE I've tried (Xcode don't have python code completion). Except the ugly* interface, it is as fast and responsive as a native OSX application.

*why they promote native look and of SWT and choose custom made tab of disputable taste?

Reply Parent Score: 1

RE: argh
by snozzberry on Tue 23rd Oct 2007 16:07 in reply to "argh"
snozzberry Member since:

Who, exactly, thought that Java on embedded systems was a good idea?
The people who invented it:
The Java programming language originated as part of a research project to develop advanced software for a wide variety of network devices and embedded systems. The goal was to develop a small, reliable, portable, distributed, real-time operating platform. When the project started, C++ was the language of choice. But over time the difficulties encountered with C++ grew to the point where the problems could best be addressed by creating an entirely new language platform. Design and architecture decisions drew from a variety of languages such as Eiffel, SmallTalk, Objective C, and Cedar/Mesa. The result is a language platform that has proven ideal for developing secure, distributed, network-based end-user applications in environments ranging from network-embedded devices to the World-Wide Web and the desktop.

The desktop versions for multiple OSes/architectures were Sun's loss-leader method of convincing vendors it was a workable, architecture-independent platform. You the consumer get it for free, but the money comes from vendors in need of licensing it for embedded applications.

Granted, it took nearly eleven years for that to become a reality (HD-DVD, BluRay) and as a "real-time operating platform" it's been surpassed by more robust RTOSes like QNX, but the article makes it clear Sun's patience is paying off.

Reply Parent Score: 1

RE: argh
by sbergman27 on Tue 23rd Oct 2007 17:18 in reply to "argh"
sbergman27 Member since:

I don't have a phone capable of running Java. But I have to wonder just how well WORA actually works on such diverse (and limited) hardware, with diverse display resolutions, input methods, ram quantity, etc.

My first encounter with write once, run anywhere, was over twenty years ago with a product called ZBasic. It had all these screen scaling capabilities and other capability mapping abstractions that sounded great. But writing the same app for my Apple ][ and my DOS box, I quickly saw the pitfalls of WORA on diverse devices. A decade and a half of making various applications work with a range of different serial terminals didn't make me any more sanguine about such things. Anyone who has ever supported WordPerfect 4.x or 5.x on Unix should know what I mean.

Edited 2007-10-23 17:19

Reply Parent Score: 1