Comments on: Partners in Precrime, Part 2

So grow your hair long, let your beard go wild and help yourself to some Lysergic acid from that dodgy-looking man in the trench coat as we once again take a trip into the Realm of Tech Fantasy…
Article Comments
(13 comments)
The following comments are owned by whoever posted them. PalmInfocenter is not responsible for them in any way.
Please Login or register here to add your comments.
RE: Glossing over nicely ;)
I'd still like to see someone have a screen full of text and, say, copy from the next to last word on a line to the next to last word on the second following line...
Fingertips are BIG w.r..t words on that dinky screen.
RE: Glossing over nicely ;)
mega-messaging, massive messaging, mighty messaging
Nice wordsmithing - really, I've enjoyed both the articles in this series. Nice the look forward. You could keep yourself busy just digging into each of those companies' activities for the next while.
I actually posted a link to each of the articles in my own little website's link page. Check it out at http://palmprefix.com. You're writing was the first thing that kept me reading here. I've tried to do the same over there. I'd love to know what you think.
Thanks again. I'll be back for round three.
RE: mega-messaging, massive messaging, mighty messaging
that's a nicely put-together site, it's now bookmarked, rss'd and Facebooked - the latter of which entitles you to see my wonderfully, horribly graphic profile pic of me in Speedos. That's what you get! :P
RE: mega-messaging, massive messaging, mighty messaging
which entitles you to see my wonderfully, horribly graphic profile pic of me in Speedos.
That's just wrong. Seriously wrong.
"twrock is infamous around these parts" (from my profile over at Brighthand due to my negative 62 rep points rating)
RE: mega-messaging, massive messaging, mighty messaging
"twrock is infamous around these parts" (from my profile over at Brighthand due to my negative 62 rep points rating)
RE: mega-messaging, massive messaging, mighty messaging
Which app wins?
Substitute any of the other on-device devices; same question.
RE: Which app wins?
Latest Comments
- I got one -Tuckermaclain
- RE: Don't we have this already? -Tuckermaclain
- RE: Palm brand will return in 2018, with devices built by TCL -richf
- RE: Palm brand will return in 2018, with devices built by TCL -dmitrygr
- Palm phone on HDblog -palmato
- Palm PVG100 -hgoldner
- RE: Like Deja Vu -PacManFoo
- Like Deja Vu -T_W
Glossing over nicely ;)
If there is no native application access (more to point, a C compiler.. could just 'compile' to JS, or to native code. Whatever.) then it means a lot of existing code (for Palm OS and otherwise) needs total rewrite before being useful. For games, you're not going to get a Quake port 'just like that', but lets talk productivity apps like Docs2Go..
Devs won't be inheriting any of their old code; a lot of good code is easily portable, even if it was old Palm OS code - lose the UI, adopt the good parts to reusable library code, and add a new UI. Thats not going to happen if we're stuck with JS. (Not to say JS is bad, but its not going to buy you any old code, and it is a performance bottleneck for some applications. Anyway, not my target here.)
So you say 'we can expect ...' - well, only if DataViz has a special relationship with Palm (obviously they do ;) and a lot of lead time to recode eveyrthing in JS, or else a back door so they can re-use old code. If they're left using JS, its going to take a long long time to get all that functionality reimplemented from scratch. (And for non developers out there .. this isnt't being lazy. Old code has a history and likely has been debugged.) Certainly, I've got tens of thousands of lines of business logic for some of my apps that would be nice to just bring over and write the new UI for.. but it means so far that all apps are ground up new. (Which in a way is nice, since you are forced to reconsider everything.. but it sure makes for a lot more work, which translates into 'time to market' and 'cost to market'...)
These are very large questions we devs are all waiting on.
Will there purely be JS access to the device, forever, or will this be a staged release a la Apple - first JS, then down the road, a heavy duty API for those needing to write device drivers or high performance computations or the like.
jeff
The Shadow knows!