>My understanding is that in the NET world, the journey (development language) is a matter of personal preference but it's the destination that counts- meaning the resulting assembly and the functionality it offers. Whether it came from C#, VB, Eiffel, Cobol or Visual Foobar, who cares? This allows VFP developers to migrate en masse to the NET arena, bringing potentially millions of lines of code with them. Where is the victim?
>
>Why is that a curious question? Silverlight is supported on mobile platforms and I think it won't be much longer till we see wpf on them also.
>
>I could say that functionality is "crippled" to use your own term. But I think you're on the right track. Personal devices *are* the future and if you check you'll see that I've been predicting that for almost a decade. ;-) If you're at the cusp and it seems you are, you have the opportunity to write a really cool mobile app to be micro-leased or sold for a buck or two, potentially giving you enough $ to retire. If that does happen, I expect a standing invitation for a fishing trip on your launch to have a drink with Kevin Goff. ;-)


From your lips to God's ears...