On Friday 08 October 2010 1:44:16 pm geremy condra wrote: > On Fri, Oct 8, 2010 at 1:38 PM, John Goodleaf <[email protected]> wrote: > > Huh. I hadn't seen that. It's a little disappointing, but, I guess, not > > especially surprising. I've never used IronPython, but I was always happy > > to know it existed, so that if I were ever stuck with a .NET project, I > > wouldn't have to re-learn, or use, C#. > > Still, if IronPython could solve my problem, RIGHT NOW, I don't think I'd > > go on walkabout with MatLab. > > I agree, BTW, that it seems a bit silly for a security team to shore up > > an Access db with arbitrary security policies. Seems like constructing a > > moat and wall to keep strangers away from your mobile home... > > J > > I was wondering about this not too long ago. A similar article > appeared on one of the python lists, can't remember which, and it > struck me as ominous that none of the IronPython developers (several > of whom frequent the list) stepped up to challenge it. > > Geremy Condra
Well I think the important part of the article is: "Microsoft last month released IronRuby, IronPython, and the Dynamic Language Runtime (DLR) under an Apache Software Foundation (ASF) license, releasing them from Microsoft's Permissive Licenses (Ms-PL). Microsoft cited customer feedback as the reason for the change, but the move suggests that Microsoft is done with trying to build the languages itself. It either wants to let the languages slowly die without claiming responsibly, or hopes the new license will finally invite others into the effort and free it from the burden of developing and maintaining the languages and runtime." Basically MS is releasing the languages back into the wild. If they survive and thrive then my guess is they will get interested in them again. -- Adrian Klaver [email protected]
