4 ms·
The problem with write once run anywhere is that it's not desirable to device manufacturers apart from those on the bottom rungs who don't have a big enough dev
by jiggy2011 14y ago
The problem with write once run anywhere is that it's not desirable to device manufacturers apart from those on the bottom rungs who don't have a big enough developer community to carry the devices on their own. If MS and Apple threw JVMs onto their devices then we would be 90% of the way there already.
If any write-once-run-anywhere solution becomes to popular then the likes of MS or Apple will try their best to kill it.
See: Embrace, extend , extinguish by MS on Java and to an extent the web itself and Apple's ban on language runtimes/interpreters on the app store.
If every device allows for the same functionality as other devices due to identical software then manufacturers will only be able to compete on price.
- stcredzero 14y ago> If MS and Apple threw JVMs onto their devices then we would be 90% of the way there already. As a one-time proponent of write-once-run-anywhere solutions, I would have to say this would probably result in a reduction of UX quality.
- cageface 14y agoI think the MonoTouch guys are handling this in the only sensible way. Non-UI code is shared across platforms but UI code is written per-platform using the native toolkit. I think this is about as close as you're going to get without compromising user experience.
- stcredzero 14y agoThat is indeed the only sensible way.