How dangerous can be programming for Kindle?

noisy · 12-09-2011, 08:33 AM

I want to split this in to two topics:

I know that developers can create Kindlets using java. AFAIK, registration on http://kdk.amazon.com/ is required. I heard that Kindlets can be dangerous. For instance statics are NEVER freed, thread with infinity loop is never killed.

Is that true?

However... I guess, that programms can be created in another native languages(C/C++?). I know that console IRC client, Irssi can be lounched on Kindle. Irssi was writen in C... What about statics and neverending threads in this area?

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, 08:33 AM	#1
noisy Member Posts: 22 Karma: 12 Join Date: Oct 2011 Device: kindle 3	How dangerous can be programming for Kindle? I want to split this in to two topics: I know that developers can create Kindlets using java. AFAIK, registration on http://kdk.amazon.com/ is required. I heard that Kindlets can be dangerous. For instance statics are NEVER freed, thread with infinity loop is never killed. Is that true? However... I guess, that programms can be created in another native languages(C/C++?). I know that console IRC client, Irssi can be lounched on Kindle. Irssi was writen in C... What about statics and neverending threads in this area?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Free (Kindle/Nook/Sony) Dangerous Angels w/Bonus Materials [YA Urban Fantasy]	ATDrake	Deals and Resources (No Self-Promotion or Affiliate Links)	1	01-12-2012 01:13 AM
Kindle - C/C++ programming	sergeyvl12	Kindle Developer's Corner	11	12-09-2011 02:04 PM
Kindle programming 101 - How to build one?	M3m0ryHunt3r	Kindle Developer's Corner	1	12-02-2011 04:42 PM
Free Book (Kindle) - The Dangerous Dimension	koland	Deals and Resources (No Self-Promotion or Affiliate Links)	3	04-15-2011 09:35 PM
Kindle DX and Programming books	fulcrum	Amazon Kindle	4	01-12-2010 04:30 PM

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)