Vineel Shah wrote:
> Well, since this thread has become a forum for rambling and subjective
> opinions, I may as well voice mine. :-) Feel free to disregard -- it's just
> about *feelings*.
.. and past experience that may not have any relevance in present time.
> I'm not saying that the WinAPI is modern, but between COM and MFC and the
> huge developer community, you can be amazingly productive.
This is exactly what killed WinCE 1.0 and 2.0. The jury is still our on PocketPC
(a.k.a. WinCE 3.0). All of these object
abstractions and stack imitation trying their best to hide the fact it is a customized
DLL is way to cumbersome in OS overhead.
> (And fields scroll BY THEMSELVES!) Programming the Palm has been like turning the
>clock
> back to 1985.
Well it is a 68K machine running at 16 MHz! At least this time, the upper management
has the common sense not to call it a
religion.
> The API was designed procedurally and doesn't adapt itself
> well to object-oriented programming (with all those nasty object-hostile
> callbacks.) C++ doesn't play too nicely with handle-based memory. Yadda
> yadda. C++ still helps, if you know it well enough. A really good framework
> would help a great deal! (A bad one would just suck.)
In agreement there. I just hope anyone that ported the MFC to Palm is keeping it in
private for their own enjoyment.
>
> When we have high-bandwidth wireless networks, we're going to need real threading to
> handle the communications throughput. This mess of timeouts and wishful
> thinking is going to kill Palm in the wireless arena, unless they do
> something about it. It doesn't really even work at current modem speeds.
I agree there too. Be remember, PalmOS 4.0 is rumored to be addressing exactly that.
I'd bet a beer there will be at least some
sort of limited multithreading where a third party app can at least register a
callback for async commo.
Steve
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
