MobileRead Forums - View Single Post - How dangerous can be programming for Kindle?

hawhill · 12-09-2011, 05:01 PM

I wouldn't call neither "dangerous". The Java side has its caveats, but in the worst case, you would have to reboot (or restart framework, to be exact).

For native applications, the situation is different. Of course, you can also create endless loops, claim a whole bunch of static memory, etc. etc. You could create good ol' fork bombs and all that stuff. The platform has no belts to stop you there, you're already behind the lines. But then OTOH there's no difference to the apps running on your desktop computer.

So the most dangerous things about either is hurting battery life and performance (both not permanent), maybe forcing you to do a reboot. Well, the usual stuff that happens when code is written badly. And remember, all code is. Even Amazon's :-) (yes, this is more joking than anything else, but there's a true thing in it)

12-09-2011, 05:01 PM	#2
hawhill Wizard Posts: 1,379 Karma: 2155307 Join Date: Nov 2010 Location: Goettingen, Germany Device: Kindle Paperwhite, Kobo Mini	I wouldn't call neither "dangerous". The Java side has its caveats, but in the worst case, you would have to reboot (or restart framework, to be exact). For native applications, the situation is different. Of course, you can also create endless loops, claim a whole bunch of static memory, etc. etc. You could create good ol' fork bombs and all that stuff. The platform has no belts to stop you there, you're already behind the lines. But then OTOH there's no difference to the apps running on your desktop computer. So the most dangerous things about either is hurting battery life and performance (both not permanent), maybe forcing you to do a reboot. Well, the usual stuff that happens when code is written badly. And remember, all code is. Even Amazon's :-) (yes, this is more joking than anything else, but there's a true thing in it)