Hi Alex,

I also had thought speed would be an issue, but the IronPython folks have found that Python written on the CLR is in many cases faster than native Windows Python. The difference between that situation and earlier accounts of .Net begin 50% slower than VFP in things like displaying forms (gasp!) may be due to the fact that .Net 2.0 contains important optimizations (a process which reportedly will continue).

Sedna is important to us, for sure.

Hank
>Hi Hank,
>
>Once we are able to access all .NET classes from VFP there may not be that many advantages to VFP being based on the CLR. Perhaps we would not lose the local data engine after LINQ is implemented or macros once the CLR supports dynamic languages, but we would probably lose performace and the wonderful way of doing things the VFP way.
>
>Once MS accepts (to itself only, of course) that a local data engine and a dynamic language are "good ideas" it is a sure thing that VFP's key advantages will live on in many products. The current roadmap may actually be pretty good for us.
>
>Alex