Quote:
Originally Posted by silver18
I'll think about it for the next release: it affects a critic part of the app, i.e. the fact of not being able to get out of the damn WAF to actually read files!
|
Side note: I know that you have thought about this a few times before. So how about developing a Kindlet with the same functionality?
On the down side: It will again be totally different, and it will most likely require to write everything from scratch again, in a different programming language with totally different programming paradigms.
On the up side: Java still seems to be the language of choice for "official" Kindle/Kindlet development. And (I'm only speaking for myself here) it is the most productive programming language I have seen so far ("productive" in the sense of "amount of correctly functioning code per developer hour", because it is clearly specified, has a huge and very well-documented built-in system library, and there are lots of external libraries around, if needed). And last but not least, it's currently the language that has the highest demand for professional developers (at least in Europe).
That said, your effort, and the result of it, is really great! Especially if, as you have been saying a few times, you have started this without knowing anything about it in the first place, and are actually learning as you go. You are the kind of person that this forum needs, and I wish that everybody's mindset here was like yours.
Thank you for your contribution.