Of course. But right now, that's vaporware. What are you going to use _now_ that has the right feature set and ability to sync to a desktop?

A clunky VM is, IMO, a good thing. It's not as good as native apps by a long shot (not even as good as Win16 apps on OS/2 ... the problem there was that Win16 apps were good enough that you didn't _need_ an OS/2 version; here, the display limitations of how the VM displays palm apps might just be enough difference to keep that from happening) ... yet it gives access to legacy apps/data to get you through until the existence of a native app. It is middle ground. It is something you can use _now_.

IMO, it's not about whether or not Access should provide this VM, and whether or not we should use it. It's "how do we get the app vendors to see that they've now got a market opportunity". If they attract users to the app that runs under the VM, then they build a userbase which will both demand, and justify, making a native version.

So...

1) find palm versions of apps you wish you had on maemo
2) contact the vendor about running it on the garnet VM
3) start pressuring/lobbying them to make a native version


(oh, and, if Nokia starts to wonder if this is going to be another Win16/OS2 situation, they should attack it from the other side: use the same strategy to lure vendors to porting native apps to maemo, fill in the missing pieces like desktop sync'ing software, etc.)