Building Blockchain Apps: https://www.buildingblockchainapps.com/
Rust and WebAssembly on the server-side: https://www.secondstate.io/ssvm/
Originally posted by a sanjuan:
the problem, i think, stems from the confusion among many people regarding j2me. a lot of people equate j2me=midp, so when they are talking (and complaining) about "j2me", they are in fact simply referring to "midp/cldc".
Building Blockchain Apps: https://www.buildingblockchainapps.com/
Rust and WebAssembly on the server-side: https://www.secondstate.io/ssvm/
Originally posted by Michael Yuan:
Sure J2ME is much more than MIDP. But I think MIDP will be the most important profile in the long run, even in the gaming sector. That is because small and simple phones are the most pervasive devices and people will carry them everywhere. You might not carry a $500 high end device when you go to beach but you will carry your $20 phone.
If you want to design a wireless game, you want it to reach millions on the move rather than competing with console games for the same pool of sitting room gamers.
So, I think the problem for wireless games is not a 3-D graphics technical issue. It is to come up with and market a game people can become addict to on small screens.
Originally posted by Michael Yuan:
Sure J2ME is much more than MIDP. But I think MIDP will be the most important profile in the long run, even in the gaming sector. That is because small and simple phones are the most pervasive devices and people will carry them everywhere. You might not carry a $500 high end device when you go to beach but you will carry your $20 phone.
Originally posted by Mark Herschberg:
I think the phone running PersonalJava at JavaOne 2001 suggests otherwise. I have no idea what it costs, but I'm sure it'll cost half as much in a year or two. Moore's Law has a way to go for moble devices.
--Mark
Building Blockchain Apps: https://www.buildingblockchainapps.com/
Rust and WebAssembly on the server-side: https://www.secondstate.io/ssvm/
Originally posted by Michael Yuan:
So, I think the problem for wireless games is not a 3-D graphics technical issue. It is to come up with and market a game people can become addict to on small screens.
Originally posted by a sanjuan:
ok, things i'd definitely want to see in MIDP is: (1) web services support.
(2) ability to interact with SIM cards and/or external smartcards through APDUs
(3) some javaphone APIs to allow interaction with calls, etc (or am i going too far here?)
Building Blockchain Apps: https://www.buildingblockchainapps.com/
Rust and WebAssembly on the server-side: https://www.secondstate.io/ssvm/
Originally posted by Michael Yuan:
1. We already have web services support through kSOAP and kUDDI. JSR 172 is making standard APIs (do not know how long it will take them!)
2. JSR 177 is such effort. I hope it could support SAML for web service single logon.
3. The new MIDP 2.0 allows you to pause your MIDlet and make a phone call automatcially using Java code. Of course, it would not *understand* the calls. We are a long way from voice recognition on handholds.