Oh, and another thing that would be a great idea in my book: J2SE, when faced with a feature that not all target platforms have, usually chooses to excise that feature from the landscape altogether. There's no ncurses-like library for java that allows you to change the location of where the next System.out line will go to. Until recently, there was no way to do any sort of serious file management other than the very basics that all OSes offer. There are no bluetooth libraries. No GPS libraries. No real video libraries. And all that jazz.
J2ME on the other hand, just spins off another subset and add a method to check if the feature is available. So, quite unlike J2SE, you can do bluetooth on J2ME. There needs to be some sort of integration for these concepts. The J2ME based libraries for very specific features that most platforms - dont- have, need to come to J2SE, along with an architecture to ask: Is service 'foobar' (e.g: bluetooth, video this, video that, take pictures, record video, grab a mike, have a look at the phonebook, etcetera) available? If yes, load this class, if no, then don't load it, or load this dummy class as an alternative. It would be very cheap - if a platform does not have a certain service, then you don't even need to add the code. You don't need to add anything - the 'loadXIfServiceExistsOtherwiseLoadY' method will simply load the alternative if the identifier string you specified isn't available on the platform. It would also help if you could offer to provide a service (should tie in nicely with jigsaw). That way, someone could, say, write a library that pinged the Mac Os X address book, or grab the webcam on windows, yada yada. This code, because it's targetted at platforms, can employ as much JSNI as it wants without fear that the non-portability is going to get in the way. On Feb 17, 2:38 pm, Jess Holle <[email protected]> wrote: > Brian Frank wrote: > > You are correct - J2ME is still basically stuck at a subset of 1.4. > > Unbelievable as that it is, those of working with embedded systems are > > still stuck in 2002. > > > Personally, I find the fact that there is even the notion of a J2ME > > silly. If Java had a proper module system in the first place, then > > J2ME would just be the kernel/VM module and could have easily tracked > > the core language. > > The notion of J2ME would still be there, I believe, but just be easy to > keep in sync with J2SE. > > Whether or not they made it easy on themselves, though, it is hard to > justify leaving J2ME back in 2002 -- /especially /with all the renewed > focus on mobile via JavaFX mobile, etc. > > Above and beyond anything else, leaving J2ME back in Java 1.4 > unnecessarily fragments Java mindshare. Anyone but the most > stick-in-the-mud, ultra-conservative (those on old versions of > WebSphere, this does mean you amongst others) should be on Java 5 or > higher -- except, of course, that Sun gives the J2ME world no choice, > thus forcing part of the Java community to live in the past and making > it harder for all of us to move forward together. > > -- > Jess Holle --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
