I am starting to interface with a product that is written in .NET. I was planning on working with IronPython, but I believe I can still interface with the API using Python. In your opinion what does this mean for IronPython? Obviously it is still usable. Kind of like FoxPro. Maybe we should call ourselves the Grateful Dead Language Developers. ;^)
On 08/08/2010 07:11 AM, Ed Leafe wrote: > On Aug 8, 2010, at 9:07 AM, Malcolm Greene wrote: > > >> The story about an incredibly small, dedicated team within MS producing >> amazing results and being shut down sounds vaguely familiar. Hmmm .... >> :) >> >> Makes me glad I avoided the temptation to look at IronPython. >> > > IronPython is a good alternative if you *have* to work in .Net, but it > never was reason enough to take the plunge into .Net. > > The thing that sucks more about this was that Microsoft never went out > and evangelized Fox to non-MS devs as a method of drawing them into the fold, > as they did with the dynamic languages. The last few PyCons have featured > speakers from Microsoft touting the power of IronPython in Visual Studio, for > example. > > > > -- Ed Leafe > > > -- Jeff --------------- Jeff Johnson [email protected] (623) 582-0323 www.san-dc.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/[email protected] ** 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.
