Paul, >> Now that those companies have years invested in .NET development, and the shops are doing things the .NET way, Microsoft no longer has any business interest in investing in the DLR, since those companies are no longer considering other development environments. Those that are in .NET are basically committed to .NET; those that are elsewhere are basically committed to their particular environments. There is no *marketing* reason anymore to keep investing in the DLR.<<
I was originally thinking developers can move to one of the other implementations of Ruby or Python, but after seeing some code at DevLink I see it has too many calls to the .NET Framework that probably won't port cleanly. I also thought people might see the abandonment as a kick in the teeth and scramble to figure out a way to move to another platform, but if you look at the situation as a "first" instead of the bigger picture trend, you might forgive and move on like many in the Fox Community have. Minimally though, people should see Microsoft as notoriously bailing on 1.0 revs over the last 5 years. Years ago we figured out that Microsoft did not get it right until version 3.0, but now you question any commitment they have until they are on version 3.0, and even that might be on unstable ground. One of the interesting notes at DevLink during the keynote, Tim Huckaby (former FoxPro developer and a current Microsoft MVP and Regional Director) questioned how long .NET will even be around now that it is 10 years old. This is something I have been asking for the last couple of years. The grind just keeps on going. Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul McNett Sent: Monday, August 09, 2010 01:24 PM To: [email protected] Subject: Re: [NF] Microsoft not so committed to dynamic languages anymore? On 8/9/10 7:30 AM, Ed Leafe wrote: > The market for the DLR, OTOH, was growing, thanks in no small part to Microsoft's active push to attract developers to it. Their decision to abandon their DLR development was certainly not driven by a dying market that developers were abandoning, as is the case with Kodak's film market. Instead, it seems much more like the abandonment of the Visual FoxPro market: lots of enthusiastic developers that they felt were now "caught", and the desire to move them into higher-profit, more restrictively-licensed tools. They used the DLR to suck in engineers working inside companies that would otherwise have successfully switched their shops away from .NET completely. Now that those companies have years invested in .NET development, and the shops are doing things the .NET way, Microsoft no longer has any business interest in investing in the DLR, since those companies are no longer considering other development environments. Those that are in .NET are basically committed to .NET; those that are elsewhere are basically committed to their particular environments. There is no *marketing* reason anymore to keep investing in the DLR. IOW, as Ed said, it is all about marketing. Individual Microsoft employees were just doing their job, but as a company they had this story arc planned out all along. You can call it "just doing business". I call it evil. Paul [excessive quoting removed by server] _______________________________________________ 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/00fe01cb37fb$b2932da0$17b988...@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.
