Slashdot is powered by your submissions, so send in your scoop

 


Forgot your password?
Close
typodupeerror
×
Programming Microsoft Software Apache

Microsoft Open Sources .NET Micro Framework 320

Posted by timothy from the what's-your-angle-college-boy dept.
An anonymous reader writes "Back in July, Microsoft announced it was making .NET available under its Community Promise, which in theory allowed free software developers to use the technology without fear of patent lawsuits. Not surprisingly, many free software geeks were unconvinced by the promise (after all, what's a promise compared to an actual open licence?), but now Microsoft has taken things to the next level by releasing the .NET Micro Framework under the Apache 2.0 licence. Yes, you read that correctly: a sizeable chunk of .NET is about to go open source."
This discussion has been archived. No new comments can be posted.

Microsoft Open Sources .NET Micro Framework More

Microsoft Open Sources .NET Micro Framework

Comments Filter:

  • My first question would be... (Score:5, Interesting)

    by Q-Hack! ( 37846 ) * on Monday November 16, 2009 @05:43PM (#30123010)

    Just what is Microsoft's angle? Surely they are gaining some advantage here.

    • Re:My first question would be... (Score:5, Insightful)

      by CannonballHead ( 842625 ) on Monday November 16, 2009 @05:45PM (#30123028)
      More people using .NET would be a gain, wouldn't it?

      • Re: (Score:2)

        by Yvan256 ( 722131 )

        Isn't .NET a back-end thing? And if it's open, then it doesn't mean you're forced to use anything from MS on the back-end either.

        So, what is to be gained? The ability to say they have x% of the server market or something?

        • Re:My first question would be... (Score:4, Insightful)

          by Lord Pillage ( 815466 ) on Monday November 16, 2009 @05:52PM (#30123132)
          The ability to sell support services.

        • Re:My first question would be... (Score:5, Insightful)

          by CannonballHead ( 842625 ) on Monday November 16, 2009 @05:53PM (#30123146)

          I'm not a .NET developer... but I seem to remember having to run .NET applications with the .NET framework on my local machine?

          I'm not sure how much Microsoft gains by keeping .NET closed-source. Perhaps that's a good question, too: why not open source it. I don't think you have to pay anything to do .NET development, do you? So may as well get any free improvements from the open source community. ;)

          • Keeping it closed source keeps people from easily porting the newest versions of the framework to platforms other than windows?

            I write against the .net framework, but not mono, because mono can't keep up with MS's framework. That also means that my apps don't run anywhere but on windows machines.

            I have nothing against mono, I just can't afford to work in what amounts to a 4 year old version of the framework.

            • Re:My first question would be... (Score:4, Informative)

              by Xabraxas ( 654195 ) on Monday November 16, 2009 @07:05PM (#30123964)

              I have nothing against mono, I just can't afford to work in what amounts to a 4 year old version of the framework.

              Bogus. Mono is very current with .NET and has even beaten MS to the punch on some features. The major missing features compared to .NET are the MS specific libraries and proper current Silverlight support. So unless you're developing Silverlight apps or Windows specific software (which would obviate the choice to use Mono anyway) I doubt you have even tried Mono.

              • If those are the only things you think Mono is missing, you don't know much about the differences between Mono and the MS compilers and frame works.

                First major problem in Mono: Non defragmenting garbage collector.

                You can't consider Mono a replacement when it leaves out a major reason to use the .NET framework. It will work OK for small, short lived ( as in short runtime ) apps, but when you start talking about services that run for long periods of time or ASP.NET applications, Mono sucks. Yes, it will 'wo

          • Re:My first question would be... (Score:4, Interesting)

            by dissy ( 172727 ) on Monday November 16, 2009 @10:36PM (#30125464)

            Perhaps that's a good question, too: why not open source it.

            I can give one example.

            Where I work, our ERP software is primarily coded in .NET, and needs 3.5.

            It is the only reason to stick with Windows on each and every workstation there.
            Every so often I check up on the status of Wine and .NET, only to see 2.x is only partially supported with no plans on supporting 3.

            If this lets me run our ERP client under Linux, be it Wine or Mono or whatever wrapper is needed, that will be a good number of workstation licenses that will fall out of the upgrade cycle.

            It will also let us deploy more ERP dedicated terminals on slightly older hardware that XP doesn't treat too well, and 2k is too painful to run on (Plus we only have so many licenses for 2k that aren't OEM)

            This could very well lead to a measured loss of sales. I am sure I am not the only one in that type of situation, even if it is not very common.

            Still, I am not complaining!

            • Re: (Score:3, Informative)

              by aztracker1 ( 702135 )
              See MoMA [mono-project.com], there are a number of 3/3.5 features. If you aren't using WPF/Silverlight there's a pretty good chance your ERP solution could be easily migrated.

        • Well, no matter what else, they gain marketshare. Right now, they have the best -- or at least, rumored to be the best -- development tools for it (Visual Studio .NET), so it's in their interest to promote the platform as a whole, as that means more people using their tools.

          It's the same reason it's in Google's best interest to improve the Internet as a whole, even if that means releasing a bunch of open source stuff which doesn't immediately, directly benefit them. Obvious example: Chrome was the catalyst

        • Re: (Score:2)

          by Tim C ( 15259 )

          Isn't .NET a back-end thing?

          Yes, and no - like Java, .NET is much bigger than just web apps, you can write pretty-much anything you want in it (with the usual caveat that you're probably not going to be writing anything too low-level, such as device drivers). There are plenty of client-side apps available written in .NET.

        • Re: (Score:2)

          by Draek ( 916851 )

          The best IDE for .NET development is still Visual Studio by a long shot, and licenses for it aren't cheap. Plus increasing their mindshare among programmers and all that, of course.

          • Re: (Score:3, Insightful)

            by digitig ( 1056110 )

            The best IDE for .NET development is still Visual Studio by a long shot, and licenses for it aren't cheap.

            True -- they're free [microsoft.com]. Well, not all versions, but you can get a long way with the free versions.

    • Re: (Score:3, Insightful)

      by Sinryc ( 834433 )
      OR maybe they just think that this will be the best thing for the framework. Maybe they feel that if they get more people using it, it will only strengthen their hold on the market, while making the open source crowd happy.

      • Re: (Score:2)

        by Yvan256 ( 722131 )

        If it's open, then where does the hold on the market comes from?

      • I'm good with that. I happen to like .NET (despite not being much of a microsoft fan). I find it is a pretty decent front end for the apps that run on windows.

        Having it actually go open source and be out there replacing Mono would certainly be useful to me.

    • Re:My first question would be... (Score:5, Insightful)

      by badboy_tw2002 ( 524611 ) on Monday November 16, 2009 @05:48PM (#30123084)

      Haven't people been yelling about for years how you can make money with open source? Maybe someone at MS believed them. Despite the general feeling that MS is "out to get you", a company is made up of people, and is not a big bad menace who does evil for evils sake. MS as a corporate entity has exactly one goal (the same as any other company) - make money for its investors. If they can make more money with open source then why is it a surprise they would pursue that avenue?

      • Re:My first question would be... (Score:5, Informative)

        by omar.sahal ( 687649 ) on Monday November 16, 2009 @06:26PM (#30123568) Homepage Journal

        a company is made up of people

        and it is also a company, a hierarchal organization were those lower down have to do what those higher up tell them to do. Those higher up have a pattern of behavior that justifies many of the fears on Slashdot. Groklaw is full of evidence, much of which was gained through court systems from around the world.
        So to quote Wikipedia [wikipedia.org]

        The base technologies submitted to the ECMA, and therefore also the Unix/GNOME-specific parts, may be non-problematic. The concerns primarily relate to technologies developed by Microsoft on top of the .NET Framework, such as ASP.NET, ADO.NET and Windows Forms (see Non standardized namespaces)

        So whats changed

      • Re:My first question would be... (Score:5, Interesting)

        by elashish14 ( 1302231 ) <profcalc4@@@gmail...com> on Monday November 16, 2009 @06:27PM (#30123576)

        Not only that, maybe MS believes that they can use this route to make better software too. If the OSS community can respond and show MS how much there is to benefit from opening one of their projects, maybe they'll be more responsive with other projects too.

        The OSS community should see this as an opportunity to give something back to MS for good reason. They would be less likely to stab the OSS community in the back with patent suits and the like if we can engender a true, two-way relationship. Maybe with some dialogue, we can start moving toward working in harmony instead of against each other.

      • Re: (Score:2, Funny)

        by pthreadunixman ( 1370403 )
        You're right. It's made up of stock holders that only care about their near-term return on investment; hence, evil.

    • Re: (Score:3, Funny)

      by RightSaidFred99 ( 874576 )

      Wow, you mean a multinational corporation with a fiduciary duty to return shareholder value thinks there might be some "angle" in this? Slashdot seriously needs a -1 (Durr) mod.

    • Step 1. Embrace.
      Step 2. Extend. ("New .Net 5.0: Now with new Windows-only features!")
      Step 3. Extinguish. ("Support notice: .Net 4.0 and earlier now deprecated.")
      Step 4. Profit.

      Remember Internet Explorer for Unix (and Mac?) Remember what happened to that once IE was dominant?

      • Re: (Score:2)

        by Virak ( 897071 )

        They don't need to open source the code for that. Mono is already behind and always will be. The .NET Micro Framework is a stripped-down version of .NET for use on embedded devices and such. It only has a small subset of the whole .NET library, and the VM itself is much simpler. Opening up the code gives away none of the interesting stuff, and probably nets them greater market share. There's absolutely no downside for them. There's also really no downside for the free software community, but they don't gain

    • Just what is Microsoft's angle? Surely they are gaining some advantage here.

      That's easy: Free code from their newly-minted community.

      One of the advantages that a company going FOSS has is that the company gets a potential for hordes of non-employees to help them code their product. Or, at least that's how the concept goes. Reality usually delivers a bit less, often a lot less. YMMV, but I suspect that Microsoft is banking on getting a whole bucketload of free dev help out of this (assuming they take in patches and etc).

      /P

    • Re: (Score:3, Interesting)

      by bernywork ( 57298 )

      Windows Mobile.

      This is their smallest subset of .NET. They are already pretty much giving the code away to developers for Windows Mobile, now they are having their arses handed to them by Android and it's only looking worse. They keep going at this rate and they are going to be irrelevant. That's not what they want. So therefore they open source .NET in the hope that they can get some more traction in the market.

    • Re: (Score:3, Insightful)

      by tgd ( 2822 )

      What is their angle?

      They're a company of 40,000+ engineers, a substantial portion of which are not total douchebags, unlike how people on Slashdot seem to imagine them.

      Lots of them use open source, lots of them like the idea of open source but, like many on here, have to juggle the realities of a paycheck with their own feelings on the matter.

      When you're a company the size of Microsoft, even if you have an internal upswelling of support for open sourcing things, you have to fight both the business people an

  • I think I'm ill (Score:5, Funny)

    by cptnapalm ( 120276 ) on Monday November 16, 2009 @05:47PM (#30123056)

    I must have the swine flu. Maybe I'm having a psychotic episode. Did I wind up in a holodeck? Or the Twilight Zone? It must be one of these things because I keep having these senseless hallucinations where MicroSoft acts like a decent company.

  • Woo! Now I don't have to feel guilty when I bitch about Mono not f***ing working correctly.

    • Re:Mono? (Score:5, Informative)

      by LWATCDR ( 28044 ) on Monday November 16, 2009 @05:58PM (#30123214) Homepage Journal

      Nope this framework is for mobile devices and the 360.
      Microsoft is really dieing in the mobile space right now. WinMo 6.5 Still doesn't have native support capacitive touch screens and the Mobile world is on fire with Android and of course the iPhone.
      HTC, LG, and Samsung are all developing or have released Android phones.
      Palm and Motorola are now dropping WinMo and going with WebOS and Android.
      This is one space where Microsoft is at best an also ran and really is dropping in the race for mind share.

  • Marketshare in Mobile Market (Score:5, Insightful)

    by Ohio Calvinist ( 895750 ) on Monday November 16, 2009 @05:51PM (#30123128)
    Microsoft knows that mobile development is booming right now and their best chance to get into the market is on very accessible powerful development tools rather than the Windows OS which is quickly losing market share. If Microsoft can have mobile developers coding in .NET, having them be familiar with Windows development is trival (since the Framework obstruficates most of the OS API.)

    If the Framework gets ported to non-MS platforms, having those developers develop on Visual Studio, on Windows, in Windows eco-systems is additional trivial.

    I am absolutely certain that iPhone development is causing iPhone developers to learn and be comfortable with XCode on Mac machines while at the same time creating more skilled Objective-C coders that will be more proficent in writing normal OS X applications.

    • Re: (Score:2)

      by jhoger ( 519683 )

      Obstruficates? Is that like encapsulates, or abstracts?

      • All of the above... good catch, those would both be better choices in terms. Though I don't know to what degree Microsoft has documented what Win32 (or other) APIs are being utilized by the various methods in the framework in all cases.

    • Microsoft knows that mobile development is booming

      Drum boom bass and the party is boomin'!

    • Re: (Score:2)

      by jrumney ( 197329 )
      The standard platform for phones is the .NET Compact Framework. What is the Micro Framework intended for anyway? My guess is that this is Microsoft abandoning a product that has no market, and trying to look good in the process.

      • From TFA:

        # The .NET Compact Framework is a cut-down version of the full-fat framework, stripping out many things that aren't used in small environments. Windows Mobile devices commonly ship with Compact .NET, as does the Xbox 360.
        # The .NET Micro Framework has the smallest footprint of all, and is designed for devices with very limited resources.

        So its not even good enough for mobile phones, maybe if you want to run your dishwasher on .NET, then it might be useful - except its got a very limited set of framework classes and a cut-down GC. This is the cannabis edition, designed to get you hooked enough to need to more powerful .NET CE, and then the full .NET framework.

    • Correct me if i'm wrong but doesn't .net run in a VM which are explicitly banned from the iphone? OFC it's useful on other smartphones but unless it has sybian support i can't see it being a major player.

      • There's already a Mono [mono-project.com] compiler for the iPhone - it simply doesn't run in a VM at runtime, but is statically compiled beforehand. Apple doesn't care how the binary you submit was produced.

        I personally don't think it's a good idea to use bridge techniques like this just because you are familiar with a language, you will always lose out over truly learning the native platform.

        One other thing of note is the Unity game development framework that lets you write game behavior login in either Javascript or C#.

  • Awesome! (Score:2, Funny)

    by Anonymous Coward

    I can't express how excited I am to see how this will be turned against Microsoft.

  • OMG it is Meta EEE! (Score:5, Funny)

    by 140Mandak262Jamuna ( 970587 ) on Monday November 16, 2009 @05:53PM (#30123156) Journal
    Not satisfied with killing software competitors by the Embrace, Extend and Extinguish methodology, now they are doing it to licenses. Pretty soon Apache license will be incompatible with everything non Microsoft, inlcuding Apache Web Server. Run, Run away when you still can!

  • There is a problem (Score:4, Interesting)

    by Groo Wanderer ( 180806 ) <charlie&semiaccurate,com> on Monday November 16, 2009 @05:54PM (#30123164) Homepage

    I was initially impressed by the MS 'open' pledges, until I talked to several coder friends. Their take, paraphrased, was that it was window dressing with a lot of traps. Basically, they 'opened' the wrapper, just like they did with their Office formats.

    The problem, as it was explained to me, is that if you want to do anything useful, you have to call a bunch of things that are not opened, will not be opened, and MS can still sue your *ss off for using. One person asked how useful it is to 'open' the hypothetical call, Play_video_with_MS_proprietary_closed_codec? I mean, you can copy the functionality, but your software is only cross-platform to the extent that MS proprietary and closed codecs and other things are 'open'.

    This is nothing more than a stealth PR attempt, they will use it to say, "We opened everything up, and see, Linux still sux0rz because it can't play movies, sound, DRM, or anything else useful. We opened everything up, but the Linux model is broken, and their lazy codes won't do the right thing. If you want real XYZ, you need Windows".

    It is nothing more than opening the most useless bits, and using it as a PR hammer. Yay progress?

                      -Charlie

    • Re:There is a problem (Score:4, Interesting)

      by RAMMS+EIN ( 578166 ) on Monday November 16, 2009 @06:23PM (#30123530) Homepage Journal

      ``This is nothing more than a stealth PR attempt, they will use it to say, "We opened everything up, and see ..."''

      Or maybe it's just fear of more lawsuits from the EU.

      However, the result is that .NET Micro Framework is now open source. That's a Good Thing.

    • Re: (Score:2)

      by Draek ( 916851 )

      Funny, but that's exactly how I've always felt about Apple's Darwin. Give away everything minus the actually useful stuff.

      Except, of course, that Mono has actually done a fairly good job of replacing the 'missing' functionality with viable alternatives, so this move is less about "yay! new stuff for me to play with" and more "yay! this is sure to help the Mono guys port their enviroment to new architectures sooner".

  • Yeah, sure (Score:5, Insightful)

    by Shadowhawk ( 30195 ) on Monday November 16, 2009 @05:55PM (#30123184)
    Wake me up when they open source the main .NET framework. They put this out there because no one is using it.

    • Re: (Score:2)

      by Shag ( 3737 )

      This. The Micro Framework is for resource-constrained embedded devices... which are just about the last place you'd want to run bytecode anyway, as far as I can see. We've got tons of embedded stuff where I work, but I fail to see how controllers for mechanical bits and pieces are going to benefit from having the CLR, object classes, GUIs, etc. made available to them.

      Yes, I know they're hoping to scoop the mobile market, but which part of it - the non-smartphone (dumbphone) market?

      • Re:Yeah, sure (Score:4, Interesting)

        by ChatHuant ( 801522 ) on Monday November 16, 2009 @06:36PM (#30123692)

        This. The Micro Framework is for resource-constrained embedded devices... which are just about the last place you'd want to run bytecode anyway, as far as I can see. We've got tons of embedded stuff where I work, but I fail to see how controllers for mechanical bits and pieces are going to benefit from having the CLR, object classes, GUIs, etc. made available to them.

         
        I think they're targetting the same area as some embedded Java implementations, like MicroJava [is2t.com]. You're getting a nice programming environment (you can use Visual Studio to write C# software for your embedded app), you're getting automatic memory management and it'll offer a migration path for people familiar with larger platforms. While it's not going to be as efficient as hand-tightened C and/or assembly code, it should allow faster development for embedded applications.

        Yes, I know they're hoping to scoop the mobile market, but which part of it - the non-smartphone (dumbphone) market?

        Not sure they're interested only (or even mainly) in the mobile market; the .NET MF can run on much lower performance processors than the ones used in phones, even feature phones (i.e., not smartphones). From what I've seen most phones use ARM 9 level CPUs, or even ARM + DSP combos, like the TI's OMAP (please feel free to correct me, phones aren't an area I have much interest in). That's overkill for the .NET MF which can happily run on ARM7 level CPUs.

    • Wake me up when they open source the main .NET framework. They put this out there because no one is using it.

      It's basically already with souce code available through the .NET Reflector, down to variable and method names. The license is in your way though, of course.

  • As Admiral Ackbar warned (Score:4, Informative)

    by h4rr4r ( 612664 ) on Monday November 16, 2009 @05:56PM (#30123194)

    It's A Trap!

    • Ugh, I guess we'll have to eat this boring oatmeal...

      It's A Trap!

    • Re: (Score:3, Insightful)

      by MozeeToby ( 1163751 )

      I know you're joking and I don't mean to direct this at you necissarily but I think it should be said.

      Many companies suck. They abuse their positions and take advantage of their customers, they manipulate the writing and interpretation of laws to suit their ends, they sue innocent people in an effort to scare people into respecting their intangible rights. Slashdot, correctly, berates them when there is news about this kind of thing. We help spread knowledge of their actions and provide sometimes insight

  • Maybe it is a promo for the 2012.

    Or

    then the maya calendar has Its reason to end on 2012....
    Hell is Freezing somewhere...

  • It took some work to locate, but I knew there was skullduggery afoot...

    Microsoft has taken things to the next level by releasing the .NET Micro Framework under the Apache 2.0 licence.

    There ya go. Microsoft has cleverly made it look like they were following the Apache 2.0 license, when in reality they've got some evil spawn of their own creation that goes under the name "Apache 2.0 licence". That special Microsoft license probably says Ballmer gets to eat your firstborn, or something equally nefarious.

    Those dastardly evildoers!

  • Why not give them some cred for trying? (Score:3, Insightful)

    by drdrgivemethenews ( 1525877 ) on Monday November 16, 2009 @06:15PM (#30123448)
    You don't train a misbehaving dog to be well-mannered by whacking it one every time it wags its tail.

    • You also do not reward a dog for puking up a steak you didn't like either.

      As was pointed out elsewhere, Micro framework (not even Compact) is hardly used by anyone, nor is anyone all that interested in it. So why should they be lauded for opening something no one was wondering what was inside of?

  • Still behind the curve. (Score:3, Informative)

    by tthomas48 ( 180798 ) on Monday November 16, 2009 @06:23PM (#30123532)

    This is all about trying to gain mobile market share, but realistically all they're doing is highlighting the headache. Thanks, but I don't want to build an app in Objective C, Java, and .Net and get them certified by Google, and Microsoft, and Apple. What a headache. As usual Microsoft is arriving at the point when the whole idea of writing custom apps per phone is starting to jump the shark.

    If they would release an easy to use IE mobile virtual images like they've done for all the current IE desktop applications they might actually have something like a leg up on their competition (I know they have some emulator inside Visual Studio, but that's not the same).

    Google has a cross-platform emulator, but neither Apple nor Microsoft do. This could easily be another situation like Firefox where developers design webapps for Android and make them work passably on the other browsers.

  • I wonder what Microsoft is going to supersede .NET with and when. And which version of .NET is this?

  • <nobr> <wbr></nobr>.NET Micro Framework 74 of 10

    Wow - I didn't know they needed an entire framework just to support NOBR and WBR. Weird.

    Honestly, Slashdot, if you can't handle HTML tags in story titles, how about you take all of 1 minute to add the code that strips it out? Sheesh.

  • I thought it felt a bit chilly this evening.

  • What market uses .NET Micro? Is it for smart phones or embedded devices? If it's for smart phones, I can see this as a reaction to Apple, Android, and Palm Pre. While Windows apps still outnumber the other platforms, all the interest these days is in the newer platforms.

  • From the article:

    Microsoft isn't opening up the whole stack: the TCP/IP parts are missing because another company wrote that code, and the cryptography libraries are missing because "they are used outside of the scope of the .NET Micro Framework"

    Does anyone know how hard it is to write your own .Net classes/wrappers for the missing pieces?
    Are there any good .Net references for CLR internals? I know how Java was designed and written, did Anders or Microsoft provide any references for .Net internals outside

Slashdot Top Deals

/earth: file system full.

Close