>>What it means is that if you were planning on a long career as an IronPython developer, you need to consider alternate career paths.<<
Why would this be the case if the language and implementation are open source? Doesn't that go against the arguments you normally provide against the proprietary languages, and the reasons you believe one should strongly consider to lean toward an open source language? Or are you saying the community or some company won't pick it up and move it forward? I have heard from others that there are serious projects developed with IronPython. Maybe one of those companies will have it in their best interest to fund the project moving forward. The announcement of IronRuby losing the key developers is not exactly what is happening to IronPython. IronPython has a reduced size team for sure, and it is not a good sign, but the core team is still working on it from what I have heard. I agree that Microsoft's lame decisions to reduce effort with the DLR languages might be something to consider, but I am kind of surprised by your statement that developers should move along. Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/00ae01cb3778$4a287640$de7962...@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
