To view parent comment, click here.
To read all comments associated with this story, please click here.
viton,
"I hope strict Apple/WinRT policies will be softened one day. But on Android there are no restrictions like this."
I can hope so too, but I don't think corporations will be willing to secede their control especially once they've become entrenched middlemen. It's why I believe it's so important to resist them today.
Android is one of the more open platforms, but it's not all clear sailing there either. Some carriers/manufacturers prohibit sideloading on their android devices, although I'm not sure how widespread the problem is. B&N forces nook users to use their marketplace, even if their effectiveness might fall a bit short. I know AT&T was restricting sideloading on their android devices.
http://liliputing.com/2011/11/how-to-sideload-apps-on-the-nook-tabl...
http://androidandme.com/2010/03/news/dell-aero-continues-atts-lockd...
My information is dated, if anyone knows of a matrix that shows the current status of which devices/carriers allow/prohibit android sideloading, please link it!
Sideload Wonder Machine is software that uses a host to subvert the restriction using android's usb programming commands.
http://www.androidcentral.com/sideload-android-apps-all-you-want-si...
"The problem actually is only with native apps.
Right now web-apps development is possible even on iPad, and it will play a significant role in future."
In the context of our discussion regarding technology access and education, does having web resources make up for the lack of local development capabilities?
Luckily many households *still* have full computers such that kids who are inclined to tinker with technology at home can, but the trends show that full computers are slowly/quickly being displaced. Does anyone know to what end?
Speaking for myself only, my ability to learn about assembly, libraries, io, interrupts, graphics rendering, code generation, etc, would have been severely impeded if my parents had bought me an ipad back then (throw in a keyboard for typing) instead of a computer.
Edited 2012-10-29 05:15 UTC





Member since:
2005-08-09
I hope strict Apple/WinRT policies will be softened one day. But on Android there are no restrictions like this.
The natural "restriction" of coding on touch screen-based devices is the usability of current development environments. Keyboard/Mouse requirement is a rather poor solution. There are interesting concepts like "Lisping" nevertheless.
The problem actually is only with native apps.
Right now web-apps development is possible even on iPad, and it will play a significant role in future.
If only WebGL worked on it... (Without JB)
Now you can write almost anything in javascript - like web-"operating system", WebGL game/demo, retro console emulator, graphics editor, etc
Even if you want to feel really "old-skool", there is something for you: http://bellard.org/jslinux/
There are some online IDEs like http://coderun.com/ide or http://cloud-ide.com
The same could be done for native apps, where you can write with any device you have, build and test your app on several target devices at once with realtime video-feedback, then submit final build directly to your dev account. But I expect Apple's "SchutzStaffel" will tear such a service apart :-)
Edited 2012-10-28 22:43 UTC