Slashdot Mirror


Microsoft Launches OSS Site, Submits License For Approval

prostoalex writes "Microsoft has launched a site dedicated to collaboration between Microsoft and open source community. The site helps developers, IT administrators, and IT buyers find out what Microsoft's product offerings are, and read articles about open source such as 'Open Source Provider Sees Sales Doubling After Moving Solutions to the Windows Platform.'" Relatedly, CNet has the news that the company has submitted its shared-sources license to the OSI for approval.

50 of 261 comments (clear)

  1. RUN AWAY!! by Divebus · · Score: 5, Funny

    Do like Microsoft does with standards... run away as far as possible as fast as you can.

    --

    Most of the stuff on /. won't survive first contact with facts.
    1. Re:RUN AWAY!! by snoyberg · · Score: 5, Insightful

      So, I'll take it as a given that no one reading this would ever consider contributing code to M$ "OSS" sites. So then the only other use for us would be to utilize their code in our products. I would recommend considering the following:

      • Are we guaranteed that the code is patent-free and will always be open for continued use?
      • Does their shared-source license allow easy mixing with other FLOSS code, eg GPL and BSD licenses?
      • Is there another, more well-established solution to the problem their code is solving?
      • And considering the "stability" of M$ products, do we even trust the code to do what they claims

      For me, it would be more trouble than it's worth to use M$ code in any of my projects.

      --
      Thank God for evolution.
    2. Re:RUN AWAY!! by Ed+Avis · · Score: 5, Informative

      * Are we guaranteed that the code is patent-free and will always be open for continued use?
      You are not guaranteed that with any other free software program. In fact, it's almost guaranteed that it does infringe software patents (both those existing now, and those that will be granted in the future).

      * Does their shared-source license allow easy mixing with other FLOSS code, eg GPL and BSD licenses?
      The GPL doesn't allow easy mixing with code under any other licence, so this seems a little unfair - but yes, practically speaking it may be a problem. Mixing with MIT-style or new-style BSD code is usually unproblematic since you can just relicense that code to match the fussier licence.

      * Is there another, more well-established solution to the problem their code is solving?
      Almost all free software projects fail this test.

      * And considering the "stability" of M$ products, do we even trust the code to do what they claims
      The whole point is that you can read the code for yourself, so you don't have to trust anyone.

      I think a better list of things to consider is whether you have freedom to (1) use, (2) share, and (3) change the software. If you can do all those then it's free software, no matter which company it came from. There's no reason to hold Microsoft-written code to a different standard to other code. If it's free it's free.

      --
      -- Ed Avis ed@membled.com
    3. Re:RUN AWAY!! by snoyberg · · Score: 2, Insightful

      * Are we guaranteed that the code is patent-free and will always be open for continued use?
      You are not guaranteed that with any other free software program. In fact, it's almost guaranteed that it does infringe software patents (both those existing now, and those that will be granted in the future).

      Let me rephrase: Are we guaranteed that Microsoft won't claim that it has patented the code after we start using it?

      * Does their shared-source license allow easy mixing with other FLOSS code, eg GPL and BSD licenses?
      The GPL doesn't allow easy mixing with code under any other licence, so this seems a little unfair - but yes, practically speaking it may be a problem. Mixing with MIT-style or new-style BSD code is usually unproblematic since you can just relicense that code to match the fussier licence.

      Using GPLed code under an M$ would almost certainly be problematic. I was talking about the other way. It's a lot easier to make OSS code GPLed than GPLed code go to a different license (aka, impossible).

      * Is there another, more well-established solution to the problem their code is solving?
      Almost all free software projects fail this test.

      What does that mean? Most FLOSS software reinvents the wheel? True. But if you're looking to use someone else's code, why start at Microsoft?

      * And considering the "stability" of M$ products, do we even trust the code to do what they claims
      The whole point is that you can read the code for yourself, so you don't have to trust anyone.

      It's possible to do so, but debugging something that's as buggy as I believe M$ code to be is probably a bigger undertaking than writing from scratch.

      I think a better list of things to consider is whether you have freedom to (1) use, (2) share, and (3) change the software. If you can do all those then it's free software, no matter which company it came from. There's no reason to hold Microsoft-written code to a different standard to other code. If it's free it's free.

      But there is reason to be more suspicious of M$ code for the reasons I mentioned. If I knew for a fact that ABC's OSS code had the flaws I refer to, I wouldn't use it either. I just don't trust Microsoft.

      --
      Thank God for evolution.
    4. Re:RUN AWAY!! by HermMunster · · Score: 4, Insightful

      There's as much chance as a snowball's chance in hell of Microsoft getting much support from OSS. Utter incompetence is involved in their attempt to embrace and extinguish campaign.

      Really, they have Ballmer yelling extortion attempts at every Linux user and they have some maverick manager or programmer, that while in Asia, claiming that 2007 is the year of the death of OSS.

      These people are not only distorted, they are crazy foolish.

      Microsoft needs to just understand that OSS will sooner or later out develop them. They need to also understand that everyone is on guard like a farmer with a shotgun protecting their daughters from the Microsoft Bible salesmen.

      --
      You can lead a man with reason but you can't make him think.
    5. Re:RUN AWAY!! by HermMunster · · Score: 2, Insightful

      Utterly false. No Linux code violates other's IP. Period! Stop spreading FUD. There's no violation until a court of law states there is. As far as I can recall there hasn't been a single OSS product that was taken to court and lost a case of IP infringement. On the other hand OSS has been taken to court and become the victor, and as far as I recall nearly 100% of Microsoft's IP related cases resulted in them loosing in a court of law, some for very serious money, including near multi-billion judgements.

      So, don't go off claiming something that is absolutely untrue and that has never ever been proven in any court.

      --
      You can lead a man with reason but you can't make him think.
    6. Re:RUN AWAY!! by jacksonj04 · · Score: 2, Insightful

      Just because it hasn't been proven doesn't mean it has been disproven.

      The chances are there is some code somewhere buried in a piece of OSS (I don't care if it's Linux or not, SourceForge alone has 153,954 OSS projects as I write this) which violates somebody's IP, somewhere in the world. Large companies like, say, Microsoft make mistakes in including IP they don't own and I'm damn sure that there is code under an open licence somewhere which does the same.

      All you can state as a fact is that as far as you can recall there hasn't been a single OSS product taken to a US court which lost a case of IP infringement, meaning it wasn't proved that code infringing specific IP was in that product.

      Don't go off claiming that OSS is pure and flawless, because it damn well isn't. The concept is great, don't get me wrong. I've seen fantastic pieces of software come out of open source, a fair amount of which I use daily. But don't claim that which you can't prove.

      --
      How many people can read hex if only you and dead people can read hex?
    7. Re:RUN AWAY!! by MightyMartian · · Score: 3, Insightful

      The chances are there is some code somewhere buried in a piece of OSS (I don't care if it's Linux or not, SourceForge alone has 153,954 OSS projects as I write this) which violates somebody's IP, somewhere in the world. Large companies like, say, Microsoft make mistakes in including IP they don't own and I'm damn sure that there is code under an open licence somewhere which does the same.
      I think it would be all but impossible to develop any nontrivial software that didn't violate at least one software patent. It sure looks like it's damn near impossible to make sure that such violations don't exist, with the pathetically awful state of the patent system.

      The fact is that if Microsoft could kill Linux with all these wonderful patents it would have already. Just because something violates a patent doesn't mean that the patent should even exist at all.
      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    8. Re:RUN AWAY!! by HiThere · · Score: 3, Insightful

      Remember that Open Source isn't the same as Free Software. And that open source is something still else...and can easily be "look but don't touch".

      Given that MS is asking OSI to approve their license I'd guess that it's not like the olde open source libraries that used to be provided...where the library was distributed, perhaps, along with a compiler, but you weren't permitted to use it with any other compiler.

      OTOH: This license was written by lawyers and proposed by MS. I'm not going to trust it until years have passed, and then only after a succession of lawyers have found it harmless. (IANAL, so I'm not going to trust my interpretation of something MS had a lawyer write for them, even though I'm allowed to read it, unlike their EULAs, where you must purchase the product to which they apply before you're allowed to read them. And then you've got to accept a new, possibly more restrictive, license with each bug fix.)

      I accept that it is conceivable that MS seriously is trying to make a truce. Unfortunately, given their track record the only safe and sensible response is to, at minimum, turn a deaf ear. So I'm not going to even bother looking. It might be tempting, but being tempted and succumbing would likely be fatal (economically if not physically).

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    9. Re:RUN AWAY!! by innocent_white_lamb · · Score: 2, Insightful

      Microsoft needs to just understand that OSS will sooner or later out develop them.
       
      Sooner or later?
       
      Look around a bit. It's already happened.
       
      Hence the desperation, and all that.
       
      No, I'm not kidding. I haven't used MS software in 8 years and I'm not missing out on anything other than viruses, security problems and headaches.
       
      Sooner or later, indeed.... Sheesh.

      --
      If you're a zombie and you know it, bite your friend!
  2. Seen it before by gentimjs · · Score: 2, Funny

    Yeah, and Attorney General Gonzalez swore to tell the truth before being questioned by the senate... And we all see how much -that- meant ...

  3. The real reason by MosesJones · · Score: 5, Funny

    Is that Balmer has run out of chairs. By doing this he hopes to gain access to all the Open Source communities chairs.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
    1. Re:The real reason by Howitzer86 · · Score: 5, Funny

      He'll get my chair when he prys it from my cold dead ass.

  4. I think this should be submitted to Wikipedia.... by iknownuttin · · Score: 4, Insightful

    for their "Spin" artice as an example.

    --
    I prefer Flambe as apposed flamebait.
  5. Talent Poaching. by Prysorra · · Score: 2, Informative

    PR. Free product testing.

    Any other ulterior motives?

    1. Re:Talent Poaching. by metlin · · Score: 4, Insightful

      If you can't beat 'em, join' em?

      I mean, at the end of the day, a large chunk of OSS developers also have regular day jobs coding proprietary software for money. The money in OSS is in support, not in the end product itself.

      Secondly, OSS only works for products, and we all know how the product-service life-cycle goes. So, if Microsoft can't make money out of a product, they can make money out of a service.

      And so, even MS can now say that they are doing that "Open Source thing" when a potential customer's (tech-ignorant) management asks them.

      This is probably a first step to that end. News at 11.

    2. Re:Talent Poaching. by snoyberg · · Score: 3, Funny

      Subversion.

      Nah, I'm sure Microsoft uses their own source management tool...

      --
      Thank God for evolution.
    3. Re:Talent Poaching. by CastrTroy · · Score: 2, Interesting

      After all the horror stories I've heard about corrupted databases and using network drives as the sole means of accessing the repository with Visual Source Safe, I'm not sure if I'd ever want to use a source control system from MS. SVN and CVS are simple, well tested, and can be accessed in a about 1000 different ways, from almost every IDE and operating system. I don't see any strong points to Microsofts offerings, but I hear lots of downsides, such as being crashes, corrupted databases, and very heavy on the network. I think I remember something about having to be connected to edit code in the repository, but that's too stupid, so I must have misread that.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    4. Re:Talent Poaching. by CastrTroy · · Score: 2, Interesting

      That's why someone like Google should go to work indexing and caching their own copies of this stuff. Is there a service that lets you date files? I've always thought this was a good idea. Send a file over the internet to some organization, and they digitally sign it, and somehow include the date which it was signed. I'm not sure how easy it would be to implement something like this, or to prevent them from just signing something with some other date, but stuff like this would be useful for having verification with dates, of when something happened.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
  6. I mean, really... by Divebus · · Score: 4, Insightful

    Microsoft is now trying to catch some of the OSS halo effect... while trying to figure out how to own it... or at least trash it? Who do they think is going to buy into anything like this? I guess when your primary business model is going down in flames, you need to co-opt someone else's.

    --

    Most of the stuff on /. won't survive first contact with facts.
    1. Re:I mean, really... by mr_mischief · · Score: 4, Insightful

      They've had a hard time vanquishing OSS by embracing and extending standards, so now they'll try to embrace and extend code and licenses.

      Expect the same tactics on different fronts. It's still Microsoft, and they are still run by the same inner circle of Gates and Ballmer cronies no matter what Hilf does from his little playpen.

    2. Re:I mean, really... by replicant108 · · Score: 2, Insightful

      They've had a hard time vanquishing OSS by embracing and extending standards, so now they'll try to embrace and extend code and licenses.

      Given the recent decision by the OSI to endorse badgeware, the 'Open Source' community appear to be doing their work for them.

  7. Interesting site by ilovegeorgebush · · Score: 5, Insightful

    It seems Microsoft's approach on this site, is to twist the terminology and meaning of Open Source to link it to their products.

    From the site (microsoft.com/opensource), they've linked to a PDF explaining how SharePoint (first link, 'share' and 'open') is the 'Road To Open' and the Sharepoint Learning Kit (SLK) has been released under Microsoft's own OSI-submitted open source license.

    Could the idea be to confuse the average consumers (and buzz-word obsessed manager types) into thinking Microsoft when they hear 'Open Source'?

    Either way, it's interesting to see them formally acknowledge their opponents - again!

    1. Re:Interesting site by EricTheGreen · · Score: 2, Informative

      Worse still, with this so-called 'product' in particular. The article goes into long,loving prose describing the development of the learning kit, it's functional origins in a now-defunct product, how it provides great value to education users, promotes peace throughout the land, etc... and omits how useless it is without having already purchased a decidedly non-open and very expensive SharePoint product.

      Where is the value here for the customer? This is an improvement,how? Great, customers get a development kit optimized for producing a certain type of SharePoint object set. Just another SDK...whoop-dee-bleeping-doo. How is this different from the legion of Microsoft SDKs and APIs produced over the last 25 years?

      Same tired horse, different saddle. Not that I'm very surprised.

    2. Re:Interesting site by mrchaotica · · Score: 2, Interesting

      But what good does "Windows Sharepoint Services 3.0" do you when you need proprietary software (namely, Sharepoint itself) to actually do anything with it?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  8. Keep your friends close... by Interl0per · · Score: 2, Insightful

    Interesting strategic move, I assume they're trying to leverage the Open Source buzzword without buying in to the free as in speech model, which is where some of the more fascinating innovations in development and marketing could possibly be hatched. Will this make even a ripple in the free software community?

  9. Remind me why I give a shit? by PeterBrett · · Score: 4, Insightful

    Windows is an pathetic excuse for a platform. It doesn't even properly implement the minimal syscalls required by the POSIX standard (open, close, read, write, fork, exec).

    If they actually cared about getting more open source developers to port their applications to Windows, they'd harmonise their API with the other major operating systems (Linux, OS X, Solaris, *BSD). As it is, this just looks like (yet another) an attempt by Microsoft to paint over the gaping flaws in both their business model and their approach to software development.

    Wake me up when that changes. Until then, I really couldn't give a shit about Microsoft's supposed "friendliness" to open source software or their non-free "open" license.

    1. Re:Remind me why I give a shit? by LWATCDR · · Score: 2, Insightful

      "If they actually cared about getting more open source developers to port their applications to Windows, they'd harmonise their API with the other major operating systems (Linux, OS X, Solaris, *BSD)."
      Windows isn't Unix. NT did include a POSIX system but that bit-rotted from lack of use and was removed I believe.
      Kind of like damming VMS or the AS400 for not supporting all the Win32 calls.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    2. Re:Remind me why I give a shit? by krelian · · Score: 3, Insightful

      Windows is an pathetic excuse for a platform. It doesn't even properly implement the minimal syscalls required by the POSIX standard (open, close, read, write, fork, exec).

      Well, they don't really have to, do they? Who said that every OS needs to be POSIX compatible? If they thought POSIX was superior they would have based their system on it and not try to create a new one. Windows Services For Unix's purpose is to help in migration and not be a full POSIX implementation.

      If they actually cared about getting more open source developers to port their applications to Windows, they'd harmonise their API with the other major operating systems (Linux, OS X, Solaris, *BSD). As it is, this just looks like (yet another) an attempt by Microsoft to paint over the gaping flaws in both their business model and their approach to software development.

      Wake me up when that changes. Until then, I really couldn't give a shit about Microsoft's supposed "friendliness" to open source software or their non-free "open" license.

      Microsoft's OSS purpose is not to spread free software and love but to help educate the people who use and develop for MS software. MS finally understands that letting developers peak inside and see exactly how the API they are using does its job is educational and helps developers create better software. This of course indirectly affects the quality of MS software and platforms and as a result, their bottom line.

      Their is OSS as a software development paradigm and their is Free software. Going Free is not going to help MS one bit, showing the world their code is.
    3. Re:Remind me why I give a shit? by EvanED · · Score: 3, Informative

      NT did include a POSIX system but that bit-rotted from lack of use and was removed I believe.

      The POSIX subsystem is no longer included in Windows distributions, but you can still get it as a free download as part of Services for UNIX (SFU). (You'll also see mention of it as the Interix Subsystem and the Subsystem for UNIX-Based Applications (SUA).)

      It is continually being maintained, and MS actually seems to have put an increased (albeit still small) push of it fairly recently. There is a fair suite of programs available for it, including GCC, Bash, automake/conf, SSH, etc., and it was supplanted to (supposedly) be POSIX.2 compliant. (When it shipped with Windows, it only supported POSIX.1.)

      The big problem with it is that programs running under SUA can't access Windows API calls. This isn't surprising given the architecture of Windows, but it does mean that, for instance, you can't really have a GUI. I'm also not sure how complete the POSIX support actually is.

      Basically I suspect it's a combination of they didn't want to put it on the CD and hence slightly encourage end users to install it (the did this with Windows 98 and TweakUI and Raymond Chen said it turned out to be a disaster for their tech support lines) and the CDs of XP being too full for it.

    4. Re:Remind me why I give a shit? by EvanED · · Score: 3, Informative

      Um, no. Bait and switch is advertising something then delivering another. MS did deliver it for the versions of Windows for which they advertised it for. And of course this ignores the fact that the OP was wrong about the bit rot bit, and in fact MS has *improved* the POSIX subsystem since they stopped shipping it with Windows, but I wouldn't expect the typical /. poster to actually know that, because it actually makes MS and Windows look a little less bad.

    5. Re:Remind me why I give a shit? by EvanED · · Score: 2, Insightful

      BTW, the post you're replying to was too harsh to be meant for you. Being wrong is fine; everyone's wrong sometimes. It's just that the poster I was replying to (who's currently modded troll) was sort of being an ass about being wrong.

      I also tire of the anti-MS slant on Slashdot. I'll be the first to admit that Windows has flaws, and I have from time to time been fairly vocal about some stupidities of its design. That said, I'm one of the seemingly rare CS people who actually likes Windows. (I'm sure a lot of this is familiarity and the fact that I know how to do stuff on Windows, but I'm no stranger to Linux either.) It gets tiresome for people to complain that MS is wrong for every single thing that they do. So the "that sounds like bait and switch" or whatever bugged me a bit.

      The reply I made directly to you was the one you were supposed to read. ;-)

  10. For some reason looking at their OSS site by pecosdave · · Score: 4, Interesting

    gives me a weird feeling in my stomache. I'm not sure what it is, but I got a chill up and down my spine. I can't catagorize either feeling as good or bad, just strange. When it comes to that empire my first question is usually what's their real objective, with this one I'm not 100% sure and that scares me.

    Does this mean we actually crossed over the line as legitimate to them, or is this bait for something else?

    --
    The preceding post was not a Slashvertisement.
  11. Explanation please by pubjames · · Score: 2, Interesting

    Through that site I came across the "Microsoft Permissive License". The "conditions and limitations" of the license have this clause:

    3(B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically.

    I don't understand this - can someone explain? If you bring a patent claim against a contributor then how does that contributor have a "patent license" that then ends?

    1. Re:Explanation please by sconeu · · Score: 2, Informative

      "A" puts something patented in MS "Open Source" code. MSPL says you have a license to use that patent.
      You patent something else. "A" does something that you think violates that patent. You sue "A".
      Congratulations! Your license to use "A"'s patent has been yanked.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    2. Re:Explanation please by Todd+Knarr · · Score: 4, Informative

      It's a reciprocity clause. Suppose A holds some patents, and they've contributed them to software S and licensed them for use there. Now, B comes along and sues everybody using software S (including A) claiming that it infringes some other patents held by B. If B uses S themselves, the clause is intended to insure that B loses their license to A's patents, opening them to being counter-sued by A for patent infringement. The idea is to force a situation where a patent-holder can't block everyone else from benefiting from a piece of software while continuing to benefit from it themselves.

  12. Their long term strategy... by skinfitz · · Score: 3, Interesting

    ...is to patent Open Source.

    That's right - all your codebase belong to them.

  13. It's a trap. by DoofusOfDeath · · Score: 4, Insightful

    I haven't read the article, I haven't seen the site or the license they submitted.

    But I know Microsoft. It's a trap. Either short-term, or long-term. Somehow, this is designed to ultimately restrict our freedoms or slow down the replacement of non-free software with free software.

    You may call be bigoted, or a troll. I see my view on this particular issue as just highly conditioned from decades of experience.

    1. Re:It's a trap. by grcumb · · Score: 4, Funny

      But I know Microsoft. It's a trap.

      It wasn't meant to be. Things would have been a lot clearer to everyone, but the domain that Ballmer wanted was already taken.

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
  14. Step one in an anti-GPL 3 move? by oneandoneis2 · · Score: 2, Interesting
    I blogged on the subject recently:

    MS has a number of proprietary things that the FOSS world would like to get inter-operable. The NTFS file system. The Office formats. Etc. etc. And the EU has been nagging at them to release interoperability information for ages.

    Since MS seems to really dislike GPL v3, they could solve a lot of their problems with a simple move: Release all the code necessary to get interoperability under Linux working. Under GPL v2 only.

    Take Samba. Samaba is going GPL v3-only. If MS released some significantly-big swathes of code under v2-only that resulted in much better Linux-Windows networking compatibility, a lot of people would use the MS-code with the last GPL-v2 release of Samba: Most end users are more concerned with how well software works than with which license it's released under.

    That would leave the Samba team with two choices: Stick with GPL v3 and have a less-popular, less-functional fork of their own software. Or cave in and go back to GPL v2 so they can take advantage of the GPL'd code from MS.

    And either way, MS would be able to show to concerned parties, such as the EU antitrust people, that they have finally released the code that the FOSS people have been demanding, under the single most popular FOSS license in current use.

    --
    So.. it has come to this
    1. Re:Step one in an anti-GPL 3 move? by Darth · · Score: 2, Interesting

      except that the Samba team would then use the gplv2 code to be able to see both sides of the process and be able to more accurately document the protocol. Then they would reimplement the protocol in their own code under gplv3.

      This would do nothing to stop the gplv3 from being adopted by Samba.

      I dont think microsoft has any intention of using any version of the gpl. They are trying to get their shared source licenses approved as official open source licenses.

      I think the point of this is that open source application development doesn't harm microsoft if they can have it done on their platform and on their terms. I think it's an acknowledgement that open source application adoption for some areas and for some users is inevitable and they are trying to minimize the impact that will have on their monopolies by making the choice to use those applications not necessitate changing platforms.

      It is probably also an attempt to take open source developer mindshare away from the things they feel are the real threats in the open source community (the gpl in general; linux and the gnu tools in specific)

      --
      Darth --
      Nil Mortifi, Sine Lucre
  15. A Microsoft OSS Site? I've said it before... by commodoresloat · · Score: 5, Funny

    It's a cookbook!!

  16. MS Open source website? ooookkk by opieum · · Score: 5, Interesting

    Well this is interesting. It is the equivalent of asking a Nazi about Jews and expecting objectivity. Also MS is having trouble having people developing on their platform. They are losing developers for Mac OS and Linux. People know a sinking ship when they see one. Plus the subtle jabs they take at developers claiming that it is their software causing security problems (which is partly but not totally true) why would anyone want to develop for MS when OSS provides full flexibility. People can see the code and not come up with hackish solutions or workarounds to problems they may encounter. http://www.cio.com/article/122152/Microsoft_Window s_Loses_Ground_With_Developers_Survey_Says With Vista being a mess of compatibility and DRM/WDM/"Security" laden crap, it makes it hard for any real innovation to happen in the application space. I used to work for MS. One of the biggest gripes I heard was that drivers were always made wrong. Applications were usually buggy which caused problems with the OS. While again that is PARTIALLY true, part of the problem was the fact that I later learned (after I left MS for the real world) that coding for Windows platforms is a PITA. The closed nature makes everything a hackish effort. Workarounds here, hooks there. Linux, BSD and other open source kernels out there have easy access to the lowest level if necessary of the kernels and OS in general. This makes it extremly easy to integrate with a minimum to intermiediate learning curve (if you are coming off Visual Studio specifically)

  17. Guys, you're doing it wrong. by BlueParrot · · Score: 4, Insightful

    This is how to do it:

    "Claims that Open Source Software would be legally troublesome or low quality are completely unfounded. Plenty of large organisations are deeply ivolved with open source development and recognise its potential. As an example, even Microsoft, a company traditionally commited to the closed source model and a long standing sceptic of many open source projects, has recently started to use it for its own codebase and has launched open source initiatives of its own: . Althou the project has had some problems, some of whic were related to the inability of the closed portion of the software to interoperate with the open bit, the work proceeds and recent developments has lead some analysts to predict the company may consider using the same model for other projects as well."

    Lets see them try to argue with that one... If they claim the article is accurate they will be promoting OSS. If they claim the project has problems they are admitting that yet another of their projects is a complete failure. If they try to claim the proprietary bit is doing well but the open bit is doing bad, they will piss off anyone participating which could easily lead to a good chunk of bad press. Lets help them shoot themselves in the foot.

  18. Re:PR, Confusion, Vista Launch, the usual. by twitter · · Score: 3, Insightful

    I really wouldn't mind a new computer.

    Me neither, but we are not average users. The average user has been on the upgrade treadmill long enough to know they are working hard to stand still, but they don't see an escape yet. Many of them wish they never saw a computer and are ready to give up.

    --

    Friends don't help friends install M$ junk.

  19. Okay, this is just to much by realdodgeman · · Score: 2, Funny

    Microsoft will survive this one only because they aim so badly that they miss their own feet.

  20. Re:A Microsoft OSS Site? I've said it before... by niko9 · · Score: 2, Funny

    Crap. I meant to type To serve penguins. I guess Linux really is dead on the desktop. :/

  21. It is your destiny, Luke... by jihadist · · Score: 2, Insightful

    I am your father. Join the dark side. (The dark side is business itself, but I'm a Socialist who detests wealth used to manipulate others, almost as much as I hate low-IQ urban poor. Actually, I hate most of humanity because they're dumb and have the moral awareness of wine corks. Microsoft is doing what business does... it pushes hard for its agenda, and if it can't get what it wants, it begins sliding up next to its competitors and trying to get into their worlds, like a Kuang Mark 11 virus...)

  22. Re:BS show me the code by dkleinsc · · Score: 2, Insightful

    I find that list significant in figuring out what MS is up to: This is not for end users, or system administrators, or even programmers. It's for corporate managers and government "decisionmakers" who hadn't even heard about this whole "source code" thing until one of their organization geeks gave a talk on its benefits. Now they can say "Microsoft software offers the same benefits" because it looks like they do (like any manager is going to read the fine print), allowing the manager to argue that point in the meeting on whether to switch some servers over to FOSS.

    The other thing I can pretty much guarantee is that if Microsoft's licenses are rejected, they'll trumpet something along the lines of "OSI and FSF won't play nice with us because we're MS and they're commie bastards".

    --
    I am officially gone from /. Long live http://www.soylentnews.com/