All right, this is getting a little crazy.
I DO believe that ALL programs SHOULDN'T be interpreted on the ipaq. Most of them need to be native. What I am saying is that for people like myself, who work mostly in interpreted languages the learning and preperation curve is a lot less if we could squeaze something like java, python or perl with a gui toolkit onto one of these devices. If the learning/preperation curve (i.e. you don't need cross compilers/toolchains/makefile tweaks/etc) is lower you will probably have more casual programmers writing apps that scratch their particular ipaq itch than not. I'd like to see more ipaq apps, thats it. I think putting an interpreted language on the ipaq is one of the best ways to get them there. That's it.
BTW: I finally got my CF card working under v0.16 (didn't work under v0.15), so now my lipaq (Linux ipaq ;-) ) is actually useful to me.
Received on Wed Sep 27 15:18:21 2000
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:42:17 EDT