IronPython is .NET... As is IronRuby and they are dynamic.

But... that's still a funky language setup especially for doing .NET stuff IMHO.

Honestly I don't understand the fascination with dynamic languages. Sure there are SOME things that are easier but for the most part statically typed languages just offer so much more support at compile time to produce more robust code without runtime debugging. Especially when you look at C# 4.0 which IMHO provides most of the good features of both static and dynamic languages in a single language interface.

I'm guessing the main feature of VFP.NET has always been the SQL DDL engine if it actually were to work. While that's nice it's hardly a deal breaker IMHO. Get over it, if that's what it is :-}

+++ Rick ---

>Hi John,
>
>I've followed dabo nearly since it was first created.
>
>For the market I reach, I need to be in .Net or Java, with a market preference for .Net.
>
>.Net also has the richest ecology, or at least the richest somewhat coherent ecology, available for application development. (Java has everything .Net has, but it's scattered here and there, hence is less coherent.)
>
>Thus my choices.
>
>Hank
>
>>Wow - I feel sorry for those that invested $ in the tech. I guess you really love MS because again you are bypassing a replacement that has been around for the last few years. I know it's not because of the python language because you are willing to use IronPython in this new tech. So that can't be the reason. So telling have you reviewed what Dabo can do?
>>
>>Johnf