Microsoft Treating "Windows-Only" As Open Source 383
mjasay writes "The Register is reporting that Microsoft is hosting Windows-only projects on its 'open source project hosting site,' CodePlex. Miguel de Icaza caught and criticized Microsoft for doing this with its Microsoft Extensibility Framework (MEF), licensing it under the Microsoft Limited Permissive License (Ms-LPL), which restricts use of the code to Windows. Microsoft has changed the license for MEF to an OSI-approved license, the Microsoft Public License, but it continues to host a range of other projects under the Ms-LPL. If CodePlex wasn't an 'open source project hosting site,' this wouldn't be a problem. But when Microsoft invokes the 'open source' label, it has a duty to live up to associated expectations and ensure that the code it releases on CodePlex is actually open source. If it doesn't want to do this — if it doesn't want to abide by this most basic principle of open source — then call CodePlex something else and we'll all move on."
This is microsoft trying to help kill open source? (Score:5, Interesting)
This is most likely a tactic to try to get people to associate "open source" with Microsoft and not Linux.
Re: (Score:2, Insightful)
Who owns this label?
Re:This is microsoft trying to help kill open sour (Score:5, Insightful)
It is not a matter of ownership. Words have a particular meaning and this is a case of MS trying to throw its weight around to change the popular understanding of the meaning of "Open Source" to something that is favorable for them. Last time I checked, "Open Source" does NOT mean "something that is only legal to use on Windows".
Re:This is microsoft trying to help kill open sour (Score:5, Interesting)
Or Linux-only, or Mac-only, or Plan9-only. The point is that if someone wants to modify the code so it runs on an Atari 800, they're legally free to do so. Publishing the code, and saying, "You may do this, only, and no more", is certainly within their rights, but it ain't open.
This is people trying to play with words. (Score:2, Insightful)
"Publishing the code, and saying, "You may do this, only, and no more", is certainly within their rights, but it ain't open."
Licenses by definition aren't open and they most certainly serve an end. All the OSI approved licenses restrict what I can do in one way or the other. Otherwise everything would be public domain which is as free as this world can offer.
Re:This is people trying to play with words. (Score:5, Informative)
The big difference in this case is that it affects how you *use* the software.
Many OSI approved licenses affect how you may redistribute the software, but none of them AFAIK limit how you may use or alter it.
Re:This is people trying to play with words. (Score:5, Insightful)
technically you are right about what licenses are. but what open source licenses all have in common is that they aim to make the software source code the most freely available to others, thus maximizing its utility, with the minimal licensing restrictions to achieve this goal.
Microsoft's use of "open source" not only goes against the spirit of FOSS, but also violates the basic definition of "Open Source" [wikipedia.org] used by the OSI:
5. No Discrimination Against Persons or Groups - The license must not discriminate against any person or group of persons.
6. No Discrimination Against Fields of Endeavor - The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.
8. License Must Not Be Specific to a Product - The rights attached to the program must not depend on the program's being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution.
9. License Must Not Restrict Other Software - The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software.
in the end, what "open source" means is defined by the community. it is what the community finds acceptable and conducive to the goals of the Open Source movement. if they decide that they are willing to accept Microsoft's definition of "open source" then the Ms-LPL can be called a genuinely open source license. however, that would require changing the current accepted definition of open source. but not only would that require arriving at a new consensus, but it would likely destroy the open source movement by undermining its original aim of fostering open collaboration and combat the increasingly restrictive IP laws and cultural attitudes.
Re: (Score:3, Insightful)
9. License Must Not Restrict Other Software - The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software.
Would you happen to know why this point was worded to be specific to other software, instead of applying to anything that might accompany the licensed software? I can say "this sofware may not be distributed with fur coats", and as far as I can see that's be perfectly OK.
Re:This is people trying to play with words. (Score:5, Interesting)
The OSD is related to what people had tried to do with licenses at the time. For example, there was Alladin Ghostscript, which prohibited its distribution on the same medium with software that wasn't freely distributable. And there was the Berkeley Spice License, for their electrical engineering software, which prohibited the use of the software by the Police of South Africa, and still did a decade after apartheid was over.
I was trying to define what was Free Software for Debian's social contract. FSF didn't promote a definition of Free Software at the time, although they'd published one in their newsletter a long time before. RMS even said in a personal email that he liked my definition.
Then 7 or 8 months after this was all written and in use by Debian, Eric Raymond brought me the news of the meeting where a bunch of people had decided to promote Free Software as Open Source, and asked me to work on that. So, I filed off the Debian references and it became the Open Source Definition, and I announced Open Source to the world, including here on Slashdot (and that announcement still survives online today). That announcement was the first real use of "Open Source" to the public.
Bruce
Re:This is people trying to play with words. (Score:5, Informative)
Re: (Score:3, Interesting)
I am supporting it but stating that, in my opinion, there is nothing that we can do.
You're wrong. Amusingly so in that the slashdot post itself points out what "we" did, and that it got MS to change something.
So what exactly makes you think we can't do anything about it, when in fact, we did?
Accepted by whom? There is no legally binding definition that everyone must accept and use. The one that you and I accept means nothing to those that do not want it to be recognised.
This is not necessarily true. Were MS to continue to call something Open Source, when it isn't, they could be open to a lawsuit for fraud, and I think they'd have a strong chance of losing. This isn't a situation where it lies in a fuzzy no-man's-land of ambiguous wording. It clearly lies outside of t
Yep, both sides (Score:3, Interesting)
If anything, it is the Free Software movement that has attempted to redefine Open Source as something other then open source. Words have meanings, and FOSS != open source, not for most people on the street. A judge or jury is going to have a much easier time making the connection to the availability of source code as open source, then showing them the 10 or 9 commandments of the FOSS movement.
Microsoft is no more guilty of misusing this term then Sun, IBM, Apple or any other large software company. The
Re: (Score:3, Informative)
Licenses by definition aren't open and they most certainly serve an end. All the OSI approved licenses restrict what I can do in one way or the other. Otherwise everything would be public domain which is as free as this world can offer.
They only restrict your ability to *close* the software (and some don't even do that).
So, no, you're absolutely wrong. Open Source Licenses don't limit rights by their nature of being a license. Those that do, do so only to promote openness. The rest (like the BSD license) exist not to create restrictions (even positive ones), but are required because the way copyright works, it's pretty much required.
Public Domain doesn't mean "free to do with as you please". It's mildly ironic, but in order for something
Re: (Score:2, Insightful)
Publishing the code, and saying, "You may do this, only, and no more", is certainly within their rights, but it ain't open.
I find that statement to be slightly ironic, since it's exactly how the GPL works, and most people consider that open.
'Course, now I'm the one playing word games, since the GPL is arguably restricting what you can do to keep openness, but still, the point is that almost all open source licenses place some form of restriction on what you can do with the code.
The difference between truly open and closed depend on what those restrictions are.
Re: (Score:3, Informative)
Re:This is microsoft trying to help kill open sour (Score:4, Insightful)
A real open source license wouldn't do that
That's your opinion. As far as I'm concerned, open source means exactly that - the source is open. People seem to be intent on tacking on a whole load of 'moral' obligations that someone has to follow to qualify to use 'open source', when nothing could be further from the truth.
Definitely a very liberal sprinkling of "Open Source is our phrase, you can't use it" going around the comments on this article.
Re:This is microsoft trying to help kill open sour (Score:5, Insightful)
It's the rights that are important. You're missing that entirely.
Bruce
Re: (Score:3, Insightful)
By your definition, the latest feature films are "open" as well. After all, you can look at them. You can't copy them, distribute them, compile them, or anything else.
C'mon, we both know you're cleverer than this. We're talking about the definition of 'open source', not open in general and certainly not Software Freedom or copyright of any kind, which is what the article would like us to get incensed about.
I respect you and your work Bruce, but I'm going to have to disagree with you completely here - I'm not missing a damn thing, and I believe you're getting yourself lost in a moral definition of a very simple English phrase - the source is open and it therefore is 'open
You are missing a damn thing (Score:3, Insightful)
Windows is a very simple phrase. Trademarked.
Apple? TM
"Start me up"? That was restricted with Win95.
etc.
And Open Source MEANS something. The use of words to mislead a customer is why trademarks were invented.
If you bought a Sony product and found out it was a Latvian company called Sony making your LCD TV, that would be wrong. Not because they didn't sell you a Sony TV but that you thought the Sony was a particular company.
Same here.
Open Source defined by OSI in computer markets.
Re: (Score:3, Insightful)
Re:This is microsoft trying to help kill open sour (Score:5, Insightful)
We need more than you think for something to be open even by your over-restrictive definition of "open". Consider that the report on the security of Sequoia voting machines has been supressed by the court [freedom-to-tinker.com]. In that case, the software was trade secret and all rights reserved. But what if it had been source code that was disclosed but still "all rights reserved"? Since that prohibits compilation and use, it would be difficult for security testers to legally do their work at all. Since it prevents derivative works and redistribution, we'd be unable to include code snippets in any report. We would be legally unable to modify the software for the purpose of testing bug fixes. And we'd be unable to distribute fixes.
The rights are a lot more important than you think. Even to have a kind of code that is disclosed mainly for the purpose of increasing trust, we'd have to design a license to convey significant rights, if the examiners were not to be placed at legal risk.
Bruce
Re:This is microsoft trying to help kill open sour (Score:4, Interesting)
My point was really that "open source" already conveys something far more simple than what you want people to read into it, and it's the simple definition that Microsoft are very obviously meeting.
Even with your more complex definition for the purposes of the OSI, the MS-LPL only fails on one count of 10, which is regarding being technology-neutral. We could further argue on how important to the issue that is but I think we'd be digressing even further from what I'm trying to say.
Re: (Score:3, Interesting)
This is interesting. How would we classify the earlier IBM OS source, MVS, VM, etc , they were "open"? They are now used for example on x86 systems. I changed and tested a lot in 70's and 80's - found a couple of bugs. Of course you were on your own if made some changes which didn't get implemented to original. BUT you couldn't sell it, just nothing preventing showing the changes to someone and they adapting the same changes - we did that a lot even between competing companies / corporations.
It was nice as
Re:This is microsoft trying to help kill open sour (Score:5, Informative)
As if that one count of 10 wasn't important.
At one point or another, my main coding platform was an Apple II, Commodore Vic-20, Commodore 64, PDP-11, VAX, Sun, SGI, PC Clone, and I've had a number of secondary coding platforms, including CHAP (something Pixar made), 6809, PIC, AVR, and so on. And all of the various operating systems for those things.
Any code that I have been given with platform restrictions, during that entire time, for various employers, is dead code today. No users, probably can't even be built if someone could find it, and I can't use it either.
In contrast, essentially all of the work I've done under an Open Source license is still living and has a vibrant user community.
You really need to think about this rights thing more.
Bruce
Re:This is microsoft trying to help kill open sour (Score:5, Insightful)
Re: (Score:3, Insightful)
First, I can read 17 USC as well as the next guy, and it's pretty clear:
the fair use of a copyrighted work, including such use by reproduction in copies or phonorecords or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright
That doesn't say, "is a defense against a lawsuit for infringement". That says "is not an infringement of copyright". So, if you are doing any of those things, you are not infringing, and you don't need a "defense".
The gray area is what, exactly, is meant by "fair use". The list of examples given shows what the law intended, but defining it specifically is maybe not as easy. Still, I'm pretty sure that saying "this code sucks becaus
Re: (Score:3, Interesting)
But, it gets to the matter of what "Open Source" is. I believe that you are promoting the idea that "Open Source" just means "Source", without the idea of "Open".
As an example, is Windows "Open Source" or not? It can be argued that Windows is, because source is made available. Therefore, for some, it is open, and that is the end of the discussion.
You can substitute VMS in there (I had it on micro-fiche), or any number of other programs.
However, consider what "Open" means -- if the software is platform-locke
Re:This is microsoft trying to help kill open sour (Score:4, Informative)
Re: (Score:2)
But (if I am understanding the comments correctly), the license forbids you from porting to code to another platform. A real open source license wouldn't do that.
Then you understand wrong and so do the tossers making the comments because the GPL allows restrictions on open source. Or are you saying the GPL isn't an open source licence?
Re:This is microsoft trying to help kill open sour (Score:4, Insightful)
The problem isn't that the code is built solely for Windows...there are lots of projects that are considered open source that are built for a single operating system. The issue is that the license expressly forbids developers to port the code to any other OS.
Call it what you will, but that ain't open source.
Look but don't touch (Score:2)
"Open source" is an ambiguous term that is almost as bad as "Intellectual Property". The objection here is that the license forbids you from doing anything with the source unless you use Windows to do it. So it's "open source" only if you already use Windows and don't ever plan to use anything else.
I can see why M$ would like that license, and it's almost comically self serving, but I have to agree that it still fits the catchall "open source" designation. It certainly isn't "Free as in Freedom" software
Re:Look but don't touch (Score:5, Informative)
That's not even the point. When someone says "open source", what do YOU think of? Let me tell you, it's not anything Microsoft related.
Re: (Score:3, Interesting)
And what's wrong with that. If you know anything about true communism, you will understand that it is actually a very sound and well thought out idea. The only reason it has always failed so horrifically badly is because of the greedy ass-hat morons that always try to implement it!
Re: (Score:3, Insightful)
And for it to be made into a Cross Platform code tree, the source would have to be completely open which is not how Microsoft is publishing this stuff. Just because the code is (supposedly) available , doesn't make it open . There's a big difference there.
Re: (Score:2, Informative)
OSI? [opensource.org]
Re: (Score:2)
Re: (Score:2)
They do seem to be quite touchy about the use of the phrase Open Source (in caps).
They really did pick a bad name though, because Open doesn't imply all the things they want it to mean.
Re:This is microsoft trying to help kill open sour (Score:5, Informative)
Open Source is what is defined by the Open Source Definition.
A number of microsoft dweebs and/or campaigners would like to have it otherwise. But then Microsoft would like to have a lot of things. It's called corporate totalitarianism.
Bruce
Re: (Score:3, Interesting)
Re: (Score:3, Informative)
Re:This is microsoft trying to help kill open sour (Score:5, Informative)
They weren't bastardizing the concept. They were working with the community to provide a definition big companies like IBM, Sun, or Microsoft, and lawyers could understand.
And in the past they even registered "open source" as a service mark for protection of the thriving community against dilution by people who wanted to twist the concept of open source.
To protect against companies who want to just make the source visible without actually opening it for others to use or change without undue restrictions protective corporate lawyers would normally demand upon (things like written approval).
Re: (Score:3, Insightful)
A case could be made that it's a trademark of the opensource initiative, and/or software in the public interest...
That Microsoft got their Microsoft Public License accepted by the OSI as an open-source license certainly indicates they know who defined the term... Then they go back and misuse it...
Re: (Score:2)
Yea but can you really trademark such a term at this point? The use of the phrase open source is so widespread now i think they've lost control of whatever power they had over its use, unless they'd like to argue over the use of capitalization Open Source vs open source.
Re: (Score:2, Interesting)
It used to be registered as a service mark of the Open Source Initiative [opensource.org].
However, I believe the trademark registration was allowed to lapse in 1999. It is a shame, because this is the type of confusion that the trademark and trademark law should have prevented.
Re:This is microsoft trying to help kill open sour (Score:5, Insightful)
Their publicity agencies are here on Slashdot pumping that angle every day.
Bruce
Re: (Score:3, Insightful)
Re: (Score:2)
Also to muddle the meaning of "open source" to the point where people start to believe it means what Microsoft says it means.
Nothing new here. (Score:3, Insightful)
Re: (Score:2)
Have a peer [opensource.org] at the definition.
Re: (Score:3, Insightful)
Re: (Score:2)
Are you starting to see the clusterfuck that is these naming schemes? And the problems seem to stem from the "open so
Re: (Score:2)
Note that i agree with you, but they would probably like for people to use terms like shared source etc.
Re:Nothing new here. (Score:5, Informative)
Re: (Score:3, Interesting)
It is possible to have disclosed source code with "All Rights Reserved", such that nobody would ever have rights to compile the code.
"All rights reserved" has a very specific meaning with respect to copyright, and not being able to compile code isn't included among those.
The phrase is actually shorthand for "all copyright rights reserved", and nowhere in 17 USC is "compling" mentioned as a form of copyright infringement.
It's exactly the same as MLB or the NFL trying to convince you that you need "express written permission" to copy a portion of the broadcast of the game. Those entities would like you to believe that their copyright rig
Re: (Score:3, Interesting)
The capital letters are not significant, if it says it's open source it has to have the rights specified by the OSD.
Says who?
Re: (Score:3, Informative)
Re: (Score:2)
It must in order to be approved by OSI, but I tend to agree with the gp that source code being available is sufficient to call something open source.
Re: (Score:3, Insightful)
While I appreciate the various efforts to define, evaluate, and compare open source licenses, I don't want someone to be declaring an absolute manifesto of what it is. I wouldn't have disagreed with your post if you said "to clarify, here is the Open Source Definition as defined by opensource.org" and "here is the mainstream recognition of what Free Software is according to the FSF." But treating these definitions as absolutes is taking it too far.
I've hosted and worked on many open source projects, and I'
Re: (Score:2, Informative)
These are common terms, and could mean any number of different things in different contexts. MS could argue that IE is "free software" for example - its not like they charge anyone for it.
Re:Nothing new here. (Score:4, Interesting)
OSI tried to register "open source" as a trademark, but didn't receive it. I don't think companies are legally bound to follow OSI's principles when describing something as "open source."
If they're using the OSI trademark or something along those lines, which Microsoft doesn't seem to be, it's a different situation.
quickly corrected (Score:5, Informative)
From http://www.opensource.org [opensource.org]
Emphasis mine.
Re: (Score:3, Funny)
I'm not surprised at all by this... (Score:2, Insightful)
Maybe they're thinking along the lines of the 'open door policy' that some managers use as a means of 'communication with employees'. I mean, it's 'open', after all... right? He might throw a chair at you, but you're welcome to step in?
Seems to me there is plenty of this sort of thing (Score:2)
...from MS that a website dedicated to it is warranted and worth linking to from everywhere.
Still Open Source (Score:2, Flamebait)
If someone can take the code, port it to other platforms, and distribute it, then it's still open source. They can refuse to accept patches porting it to other platforms, and it's still open source. Their hosting provider can even deny them free hosting if they accept patches for supporting other operating systems.
Just because you host open source, doesn't mean you can't add extra constraints. Google Code limits the licenses you can use, and used to not allow the Mozilla Public License.
Re: (Score:3, Informative)
That's the whole point, you're not allowed to do that.
Re: (Score:2)
And to add to that, there are plenty of open source projects on Freshmeat that only run on linux/BSD, or even SourceForge for that matter (which also hosts Windows-only open source projects). "Open source" is that the source is made available. Various open source licenses generally allow for edits to the code but as the parent points out, those patches don't have to be accepted. Does the linux kernel take every patch? Hardly.
There is no problem here (Score:2, Informative)
Re: (Score:3, Insightful)
No, "open source" means no license restrictions on what you do with the code. If the license forbids you to run the code on another OS, or another pieces of hardware, it is not open. Neither is it open if you prevent the use of the code for a particular purpose. If you want to use the code to tabulate a list of people who you intend to round up, incarcerate, and incinerate, people will deplore your morals, but the OSS movement in principle defend your right to use open source code to do it (but does not all
Re: (Score:2)
No, "open source" means no license restrictions on what you do with the code.
FSF disagrees, see the anti-Tivo section in the new GPL.
Re: (Score:3, Insightful)
No, damnit.
Open source means that the source is open. That's it.
You could hypothetically define "Open Source" (with capitals) however you see fit, or be a lot more specific and refer to GPL, BSD, Creative Commons, etc.
However, in this case "open source" is very simply referring to software that has its source code openly available. You cannot simply redefine the meaning of already-existing words, especially when you're not using them as a proper noun. There is absolutely no debate to be had here.
Also, wh
Meaning of words (Score:3, Insightful)
'When I use a word,' Humpty Dumpty said, in a rather scornful tone,' it means just what I choose it to mean, neither more nor less.'
'The question is,' said Alice, 'whether you can make words mean so many different things.'
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
Re: (Score:3, Insightful)
Again. As long as you capitalize Open Source, you're correct.
However, the insistence on using the most ambiguous language possible to describe an ideology has ultimately resulted in arguments such as this. RMS and co. should have avoided naming their movement using words such as "Free" or "Open," which can be used to mean something quite different.
Granted, part of this is the fault of the English language, which fails to differentiate between "libre," and "gratis," though you'd think that they'd have just
Re: (Score:3, Insightful)
No, "open source" means no license restrictions on what you do with the code.M
Every single "open source" license out there completely contradicts your statement.
Re: (Score:3, Informative)
OSI is not a governing body, so their opinion on the matter is largely irrelevant.
Re: (Score:3, Interesting)
Nothing to see here... (Score:3, Informative)
About CodePlex CodePlex is Microsoft's open source project hosting web site. Start a new project, join an existing one, or download software created by the community. More About CodePlex... Microsoft does not control, review, revise, endorse or distribute the third party projects on this site. Microsoft is hosting the CodePlex site solely as a web storage site as a service to the developer community.
In other words, developers can -gasp- choose the license they want. And they do, including MS. Also, it has nothing to do with the OSI since MS explicitly mentions it's 'open source' and not 'Open Source'(which seems to be hijacked by the OSI as a trademark?). open source != free(as in freedom) software.
Re: (Score:2)
Well said. Mod-U-Up.
Nothing new here... (Score:2)
http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish [wikipedia.org]
Bad summary (Score:3, Insightful)
From the article:
Honestly, please read more than a paragraph or two of the article before submitting it to Slashdot. You can submit any code under any licence you like to CodePlex, and indeed encourages you to do so. Where's the problem here, exactly? That "open source" means different things to Microsoft than it does to some other people? That term means many things to many people, from the idea of being able to view the source of software but do little else with it, to the BSD/public domain-ish idea of all code being available for modification under virtually any terms. That's all this is. Nothing to see here, move along.
Codeplex is a joke (Score:3, Interesting)
What is Codeplex really about? It's a cheap form of recruiting developers to keep supporting the Windows platform by building better programs... as long as Microsoft gets a profit from it.
This is why using the GPLv3 is forbidden in Codeplex [milkingthegnu.org].
not to nitpick... (Score:2)
Viral Software back at ya (Score:2)
Perhaps this is an attempt to trick developers not paying close attention into download some Ms-LPL source and include it in their project. Later, when some code snippets show up ported to another platform, Microsoft can cry foul.
Many years ago, our legal department advised us _not_ to touch Microsoft tools, products, or platforms. Or some tangled web of licensing restrictions could come back to bite us.
Like Organic Farmers (Score:3, Insightful)
This is, unfortunately, a prelude or realization that Microsoft can embrace/extend/extinguish the _meaning of the phrase_ "open source" just as well as it can anything else.
Sadly, the exact same thing happened to all the "organic farmers". Big companies started slapping "organic" on all their products because it would sell, irrespective of any meaning behind the words.
The only defense would have been to trademark "organic" / "open source" and have it be held by some public committee, but it's too late now.
Re: (Score:3, Informative)
Certainly the UK gives legal backing to the word "organic".
But it's important to note that the word "organic" does not mean "not produced in factory farming conditions". There's no reason in principle why you couldn't keep chickens in the same cramped, dark houses they're normally kept, change their food so it didn't contain growth hormones, antibiotics or any of that crap and call it "organic".
(Your chickens probably wouldn't last long enough to make it to the supermarket because in those kind of conditio
nobody should be surprised at this. It is MS-SOP (Score:4, Insightful)
come on, are people really surprised that Microsoft is not only taking MS .Net to the world of Windows-only but also making sure anyone who uses their sites/services are Windows-only partners too?
Get real folks. With out a monopoly hold on the pre-load computer market, Microsoft would be dead meat. They know they need to make sure their customers do not have a choice to try another OS because they will not put their software on another OS. Remember, without Windows they are dead meat. Outside of one package, MS Office for Mac, they have never put their software on another OS with the intention of making a business profit from it. They put Internet Explorer on Solaris to kill off all the Win32-UNIX licensees and keep anti-trust judges from nailing them for it. When Palm had 80% marketshare and WinCE was less than 5% IBM, Sybase, and other dbase vendors released lite versions for the PalmOS. Microsoft released MS Access-lite for WindowsCE.
Miguel is an idiot for kissing Microsoft's ass every time they expose it to him. MS .Net was created to stop Java from taking Microsoft developers over to a cross platform API and software stack plain and simple. Anything "open" about it is a trick/game/hoax/etc because they own the spec.
Microsoft's business is to own/control all software development and make sure it is all done on Windows. This is a fact. Everything they do must first protect the Windows marketshare. This is reality. Open source is a threat to Microsoft when it runs on anything other than or along with Windows. Another fact. So cry all you want Miguel, you're an idiot for following Microsoft and playing the Pied Piper to those too naive to understand. IMO.
LoB
Re:haha (Score:5, Funny)
I don't think it is fair that you got first post, I wish I had got first post, my first post was going to be quite good. Someone (perhaps the shashdot editors should fix this). Maybe in retrospect I should have realised that an Anonymous Coward by nature would try to get first post, but I didn't, my hope was that the Anonymous Coward would change his behaviour this time so that everyone would get to read my post - but I guess the Anonymous Coward can't be trusted to do the right thing after all. Its a shame though. I really hope that from this chastisement Anonymous Coward will get message and change his spots. Irrelevant first posts are selfish and spoil things for everyone.
Re: (Score:3, Insightful)
Hmmmm, I discovered something with the latest Ubuntu......I could install it within MS windows and run it.... like an application.
well hear this... (Score:3, Informative)
I hear there are no versions of the Linux kernel that run under windows.
From http://www.colinux.org/ [colinux.org] Cooperative Linux is the first working free and open source method for optimally running Linux on Microsoft Windows natively. More generally, Cooperative Linux (short-named coLinux) is a port of the Linux kernel that allows it to run cooperatively alongside another operating system on a single machine. For instance, it allows one to freely run Linux on Windows 2000/XP...
Re: (Score:2)
Re: (Score:2)
It really has them, but it is preferable than banner ads...
Re: (Score:2)
As long as the author of the driver from that site is the copyright holder of the original source, it doesn't matter if it was originally GPL ; the author may choose to relicense the code any way he sees fit.
I'm not saying that this is the case ; just presenting a potential means of this driver being both based on GPL code and legitimately distributed in a closed-source manner simultaneously.
But... (Score:3, Informative)
Point understood, you have an example of a ruby-only site.
However, do projects on that site have a license explicitly forbidding you from re-implementing them in python or perl or C? I suspect no, that they would allow that even if they choose not to explicitly aid it.
In this case, MS's site is hosting code that not only is Windows specific, but forbids potential developers from even porting it to other operating systems. The former is hard to argue, the latter bit I understand raising some ire amongst Fr
Re: (Score:2, Funny)
Re: (Score:2)
As long as it is fermented horse piss, I believe the stipulations are: made from grain/cereal and fermentation, and horse piss could cover both of those.
Re: (Score:3, Insightful)
If you're an awesome enough hacker to take code written for Windows on x86 and compile it on a TI99/4A, then go to. The problem here is that the licence forbids it to be used on non-Windows platforms, not that it's difficult in practice to do so.
It's similar to a trademark. (Score:2)
Re: (Score:2)
As a matter of fact, the majority of the world population has different words for free-as-in-freedom and free-as-in-beer: for the languages I know, there is Italian (libero/gratuito), Norwegian (fri/gratis), German (frei/kostenlos). So it's really because of a glaring fault of the English language, and the last thing you can blame the FSF for
Re: (Score:2)
This is one end of the spectrum of definition of "open source".
The more commonly understood definition is a license that meets the Open Source Definition [opensource.org], which MS-LPL obviously does not (contravenes point 10 at least).
It would not be outlandish to suggest that MS are trying to dilute the expectations of those hearing the words "open source" to include their more, well, useless definitions like MS-RSL which allows you to refer to the source for the purpose of increasing your understanding of the library (so
Re: (Score:3, Insightful)
Not possible. Anybody who receives the library under the GPL can port the library as he or she pleases.
If you don't realize that platform independence is a key tenet of the Free and Open Source software communities, you're missing the point entirely, and you're unlikely to be contributing positively to the discussion.