Slashdot Mirror


Microsoft May Back Off of .NET Languages

An anonymous reader writes "Though Microsoft had initially made a commitment to create versions of dynamic languages that are customized for .NET, recent reports make it clear that the company may be stepping back from this plan. Much early speculation on this change in focus comes from Jim Schementi, previously the program manager in charge of Microsoft's implementation of the Ruby software known as IronRuby. Schementi reports on his blog that the team dedicated to working on IronRuby has decreased to one employee. According to Schementi, his departure from the company came as Microsoft began to display a 'serious lack of commitment' to any .NETized dynamic languages, including IronRuby."

4 of 443 comments (clear)

  1. Good by aaaaaaargh! · · Score: -1, Troll

    So-called 'dynamic' languages suck. Now if I could only get a good static language, that would be nice. It doesn't need to be based on .Net, though, in fact, I'd personally pefer if it wasn't.

  2. Re:Getting screwed in both directions by Timothy+Brownawell · · Score: 0, Troll

    Static languages make you do more of your thinking up front. Dynamic languages make it easier to just slap things together and worry about your sanity later.

    Apparently a lot of web stuff has sufficiently trivial programming that you usually finish before you have to make a sanity check, so dynamic languages let you get off without thinking at all.

    </troll>

  3. Follow the money by mrflash818 · · Score: 0, Troll

    In my opinion M$ cash cow is their 'all corporations seem forced to use' OS and their 'all corporations seem forced to use' office suite.

    Anything else, based on the behavior during the company's history, fades away after big announcements that it will be 'the next big thing.'

    Just follow the money.

    --
    Uh, Linux geek since 1999.
  4. As a sysadmin by AhabTheArab · · Score: -1, Troll

    I want .NET to go away. It's a pain in the ass. Some programs require a certain version, but don't package it with the install. Some programs require a certain version and will break if you have a newer version of .NET installed (vSphere Client, for one example, requires .NET Framework 2.0 but will not work with .NET 3.0). I'll admit, I really don't know much of what .NET even is. The only thing I remember is a TV commercial from about ten years ago talking about .NET. Some guy was using a tablet computer, and selected the color of paint for a car or some shit.