This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: StartUps and VCs are idiiots
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
First, let me apollogize to Nokia, Siemens, Sun Microsystems, VCs and etc. What I am about to say is going to be somewhat bile laced but is backed with real experience.
In developing applications on resource constrained systems such as Mobile devices there are tiers of people that have no freaking idea that their IT tech experience does not transfer well to developing mobile applicaiotns on a reasonable predictable schedule using a software engineering process. Do not get me wrong here, Sun's WTK is an ideal tool for those just learning J2ME.
However, its usefullness in being the right set of tools in a software process that is able to predict a reasonable schedule for completing new applications on new J2me technology is not very huge beyond the compiling of the midlet. One reason is the imperfections of the API implemented in the J2ME JVMs found on the devices.
To complicate matters you have some StartUp idiots and VC idiots that think developing on a resource constrained device requires no spec because in fact the device is small.
Thus, basically because Orca TDD Build Framework by providng a framework in which we have analysis tools, full audit logging of what happens, logging on client side, and etc provides feedback we can than use that feedback to educate the tiers above us to what is technically feasible and what is not in a fast way depsite being ordered to proceed without a spec.
Sure, I could complain about the imperfections per J2ME JVM implementation but just as some Motorola embedded engineers have stated off of the record, its the boundary of J2ME JVM/APIs and the OS where the imperfections occur in a J2ME JVM. For example, certain MMAPI functions require a resolution of the OS state and of course you can get that wrong at the embedded JVM/OS level and of course Sun's TCK's do not directly test for this boundary problem.
Thus, several years of Mobile development is driving me towards completing this Orca TDD Build Framework to have a feedback system that enables application develoeprs to take control of this situation. But, why use the LGPL or GPL and give it away?
Well, if I give it away that increases the amount of feedback in the public of all those imperfections in J2Me JVMs on all devices as I am a one person dev shop without the financial resources as a JAMDAT to physically test all J2ME JVM implementations on all mobile devices. If its easy to find out the imperfections per J2ME JVM from the application developer standpoint than that discovered information will float ot alll developer fourms.
Plus, usually you do not find the imperfection until you attempt a new use of a J2ME API and at that point you want some relaible emulator data to compare against the device errros so that you can give a most clear picture to the OEM engineers for faster resposnes both in the OEM Device space.OEM OS space, and the OEM J2ME JVm space. The disappointment at this point is that I have not delivered on my benefits message to the Mobile Application Publishers in an effective way to gain or obtain outright financial funding of these types of projects which will dramtically incr4ease the new applicaitons and games that they are able to place with their Mobile Operator clients.
Previous Topic
