Hi Thomas,

Your strategy is sound for someone who (obviously) is able to be competent in a number of languages. Some of us (c'est moi) have to focus on one or two places. For me it will be Boo, IPy, and C# as a very reluctant backup. Boo for tools; IPy for development; C# to fill the holes. Although Boo for development is a distinct possibility if IPy is orphaned by MS.

Hank

>Hi Hank,
>
>>It's a mess for dynamic programmers. As per my latest blog post, multi-company support for the development of a 3rd-party language (e.g., Boo, or Cobra, or VFP.Net if that were an option) is probably the best solution. Depending on oneself (and others in the same boat) promises more stability than being held hostage by Microsoft's lawyers and middle managers.
>
>I will keep working with IPy for the moment - and have Boo and Node.Js on my radar (Scala et al. not really checked for active participation). CPython is being developed, and IPy and Jython as well as Jype give me hooks in the big runtimes, so my interpreter/dynamic needs are covered from that side. Javascript (while it is an ugly language compared to Python, Node.Js is very active and interesting) is my last resort fallback - as I came to fox first as an add-on to C and Modula2 I guess I will be able to host dynamic parts if push comes to shove. The "glueing" aspect of PYthon from Shell scripts to mathmatical libraries is one of the aspects I like a lot, even results are not always as finished as "write everything again".
>
>my 0.003 EUR
>
>thomas