Yes... But since the portions of their stack that are GPL (Linux at least, and probably others) are mostly already present in Maemo, the ones we need are the ones they may not release.

However, since it sounds like it's mainly webkit+javascript bindings, it may not be too hard to reimplement the API in an open source project; like wine, but much smaller (hence easier) project. Hopefully their API is better documented. Also, aiming at version 1, presumably with a clean design, rather than much evolution and cruft, is good.

This would leave the UI stuff (flipping between cards, etc.) not necessarily the same at all, but all (or most) apps directly runnable on most any webkit-running platform.

Forgot the link: http://www.masswerk.at/jsuix/

Exactly - right on spot - the whole concept of having to 'Sync' devices to a mother device is against the mobilly idea itself - it means you are essentially tethered to a parent device.

I really liked the idea of fetching all information on a particular contact from different sources and aggregating and showing it as a stack.
I wonder how they implement this though.

I'm thinkin' ^that's pro'ly pretty close.

This implies a heavy master/slave architecture like a thin client. This exists everywhere, from USB (more simple) to FireWire or SCSI (more advanced). However, here these don't apply because you misunderstand having. You don't have to. You want to, and are able to add clients which synchronize back and forth with each other; this works flawlessly.

If you'd have networking the changes can be applied in real-time! Then you do not have to synchronize independently anymore, but you probably run some kind of server which is the 'master'. Instead of that, as of now you have a devices which can function when disconnected. while as soon as you start networking you have potention to sync. Note that synchronisation is also possible both ways.

So, if you take it from this point of view, and include 24/7 connectivity with HS*PA, the doors to synchronisation are open even wider because it has become easier to implement it automagically, in real-time.

Simple examples: if I read my e-mail on my laptop I want to know which ones I already opened. IMAP supports this. Some browsers support this browser-wise using cookies, php sessions, IPs, or accounts. If you take something like RSS however there is no such support. If you take Calendar, you can synchronize your changes made on your tablet to your desktop after you got home. After you make changes on your desktop, you synchronize this back to your tablet, and have both up2date when you leave the house next morning.

Sprint has announced today that the Palm Pre will be available on June 6. Sprint announced that it will be available nationwide in Sprint stores, as well as at Best Buy, Radio Shack, and select Wal-Mart stores. The webOS-based phone will retail for $199.99 (after rebate and service agreement).

Some more info snagged and posted on Endgadget. The Pre launch manual for Sprint executive eye's only (or so they thought ).

BTW, that's^ how US cell phone service providers launch new phones.

This really jumped out at me:

"We can't afford to sell the Pre to the wrong customers"

(Of course, they just push them to the Treo Pro if they're the "wrong customers".)

Yup, so much for letting the market decide in a "free market" economy.

It may not matter if what the early reviews seem to agree on is true... the Pre's hardware keyboard sucks and its on screen keyboard is difficult to manage.

http://mjg59.livejournal.com/111453.html

Quite interesting, it seems that pre has git installed. Who is willing to bet its used to power synergy? Also, the layout seems fairly conventional, so i suspect nothing will stop palm from dusting of the foleo, pop in a cortex and run it using webos, with git powering any kind of sync between phone and companion...