Slashdot Mirror


How Open Source Has Influenced Windows Server 2008

willdavid writes to tell us that Sam Ramji over at Port25 has a nice succinct list of the major open source principles that have been used while developing Windows Server 2008. "Overall, we've learned and continue to learn from open source development principles. These are making their way into the mindset, development practices, and ultimately into the products we bring to market. I've focused here on 'what Microsoft has learned from Open Source' - and ironically, I've agreed to do a panel at OSBC on 3/25 with Jim Zemlin of the Linux Foundation on 'what Open Source can learn from Microsoft'. As all of the different organizations in IT continue to evolve, we'll learn from each others' best practices and make increasingly better software. As in science, this incremental improvement will move all of us forward."

145 comments

  1. What they can learn by snl2587 · · Score: 3, Insightful

    'what Open Source can learn from Microsoft'

    Wait, wait...how to release commercial software on par with an untested, alpha Linux flavor and have all their customers switch back to an old version?

    Or maybe how to give consumers what they "want"?

    1. Re:What they can learn by Anonymous Coward · · Score: 1, Insightful

      Or maybe how to give consumers what they "want"? Indeed. I, for one, am happy that the programs I was running on a Linux 1.0 kernel will run flawlessly on the Linux 2.6 kernel without modification. I'm continually surprised that the rich legacy of Linux apps will continue working unmodified because the developers put so much time and effort to ensure backwards compatibility.
    2. Re:What they can learn by maxwell+demon · · Score: 3, Funny

      How to improve on their chair-throwing skills.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    3. Re:What they can learn by rmdir+-r+* · · Score: 4, Informative

      Indeed. I, for one, am happy that the programs I was running on a Linux 1.0 kernel will run flawlessly on the Linux 2.6 kernel without modification

      You want to run buggy versions of GCC and Apache?

      All joking aside, as long as you didn't use glib/statically compiled your application, I believe Linux 1.0 apps WILL run flawlessly on Linux 2.6 kernels. The kernel's userspace ABI has been very stable.

      (Of course internal ABI/API stability has historically been on the order of six months :P).

    4. Re:What they can learn by Nullav · · Score: 1

      Nah. Let MS keep the chairs, I really don't want to have to pick a distro before sitting or throwing a childish tantrum.

      --
      I just read Slashdot for the articles.
    5. Re:What they can learn by The+Mighty+Buzzard · · Score: 1

      We already have that, it's called Gentoo.

      --
      Violence is like duct tape. If it doesn't solve the problem, you didn't use enough.
    6. Re:What they can learn by Scott+Wood · · Score: 1

      The problem with that is that most things aren't statically compiled. And no, it's not old versions of GCC or Apache that I want to run, but older games, including those by a certain porting house that went out of business and can't release patches. :-)

    7. Re:What they can learn by hackus · · Score: 0, Troll

      This is a bunch of crap.

      I call it as I see it, and this is about as crappy as it gets.

      There is no FREAKING way Microsoft can do any of those 8 things if they want to stay in business.

      So this is all PR.

      Microsoft is the poster child of lock in, proprietary closed and SECRET API's.

      I wouldn't take any of this seriously and really wonder why this even made Slashdot news.

      What a joke.

      I also do not believe any of the crapola this guy is espousing about "we can learn from each other".

      Crap crap crap.

      Open source doesn't need Microsoft PERIOD.

      If open source needs anything it is MORE PEOPLE writing MORE OPEN SOURCE SOFTWARE.

      It sure in the hell doesn't need ANYTHING from Microsoft.

      -Hack

      --
      Got Geometrodynamics? Awe, too hard to figure out? Too bad.
    8. Re:What they can learn by Shulai · · Score: 1

      You are just going out of luck. a.out loader is just being phased out of the ELF kernels.

    9. Re:What they can learn by Allador · · Score: 1

      There is no FREAKING way Microsoft can do any of those 8 things if they want to stay in business. You do realize that in the second part of TFA, they list how they've done all 8 of those things, with specific examples on each, right?
    10. Re:What they can learn by ratboy666 · · Score: 1

      Put the libraries into a directory, and set LD_PATH to point to that directory. Ensure that your kernel actually supports a.out format. Normally, you would create /linux10/bin /linux10/lib. Create a linux10run script in /usr/local/bin that executes its $0 argument as /linux10/bin/$0 with the reset LD_PATH. Of course, configuration (/etc) may give you a bit of trouble, but usually not for a game (/etc/hosts, /etc/passwd are the same).

      The X server is compatible, so it's not a problem. If the application used direct i/o, it already has suid; may be a security risk, but not much of a problem (virtual console support may be, just don't switch away from it once running). If the game uses direct i/o, it (90% confidence) won't run under VMware.

      Can't think of much else that would be a problem. Except, of course, the building of the old linux environment. You may have to download and install an antique linux. If you have SATA disks, this will be problematic. Install the antique linux on VMware Server, with IDE (a simple environment) -- and then copy the required /lib and /usr/lib .so files (you can copy both to /linux10/lib, and, given that disk space is fairly cheap, you can copy them all).

      If /etc gives you a problem, consider chroot'ing the thing.

      Have fun with the game!

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    11. Re:What they can learn by hackus · · Score: 1

      Oh you mean like the way they claim they use open standards, and as a example cite they participate in open satndards procedural bodies while at the same time closing markets, getting sued by the billions by the european union for doing exactly the opposite?

      I am a troll?

      I hope you call rot in proprietary software hell!

      -Hack

      --
      Got Geometrodynamics? Awe, too hard to figure out? Too bad.
  2. Embrace, extend, extinguish? by KublaiKhan · · Score: 4, Insightful

    Isn't their philosophy to try to take ownership of anything that threatens their business?

    --
    In Xanadu did Kubla Khan
    A stately pleasure dome decree
  3. What FOSS can learn from MS? by jhines · · Score: 3, Insightful

    So it is a listing of things NOT to do in an OS.

    1. Re:What FOSS can learn from MS? by Rary · · Score: 3, Insightful

      So it is a listing of things NOT to do in an OS.

      If you don't want your OS to become the dominant OS in the PC market, yes.

      --

      "You cannot simultaneously prevent and prepare for war." -- Albert Einstein

    2. Re:What FOSS can learn from MS? by strabes · · Score: 5, Insightful

      Windows' market share obviously has nothing to do with its quality.

      --
      Its = possessive. It's = "it is"
    3. Re:What FOSS can learn from MS? by smoothdogg00 · · Score: 1, Funny

      You must be joking... there will never be a day when the quality of any Linux distribution is higher than the latest Windows distribution. Say what you want about Vista, its a great OS. Linux is for the "non-conformists" who want to seem smart, or for those who don't want to pay for an OS.

    4. Re:What FOSS can learn from MS? by pdusen · · Score: 0

      By that logic, Linux's market share must have EVERYTHING to do with its quality, no?

    5. Re:What FOSS can learn from MS? by strabes · · Score: 1

      You must never have installed windows on a laptop. My dislike for Microsoft is not irrational; drop the ad hominem.

      --
      Its = possessive. It's = "it is"
    6. Re:What FOSS can learn from MS? by bigstrat2003 · · Score: 1

      I most certainly have. It works fine. And calling Windows a bad OS is irrational. It's not an ad hominem, ad hominem would be if I called you a moron or something. Irrational is entirely different.

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    7. Re:What FOSS can learn from MS? by V!NCENT · · Score: 0

      Actually, the only thing that the FLOSS community needs to do is learn about everything that Microsoft has ever done, and do the exact opposite...

      --
      Here be signatures
    8. Re:What FOSS can learn from MS? by opieum · · Score: 1

      Heh seeing MS track record, I wonder how much FOSS code actually is in the OS itself. Did they pilfer elements of ReactOS? WINE? SAMBA? Linux iteself? Be intresting to see if the Windows code ever were to be mysteriously leaked. And I am sure it can and will eventually happen.

    9. Re:What FOSS can learn from MS? by rbanffy · · Score: 3, Insightful

      "If you don't want your OS to become the dominant OS in the PC market, yes."

      Windows' dominance has pretty little to do with Windows per se. Microsoft got lucky (and that "luck" is remarkably disputable as it seems possible they set IBM up) when they launched Windows 3 and abandoned OS/2 development to rename OS/2 3.0 as NT. Windows 3, 3.1, WfW were very popular partly because software makers embraced them. Shortly after that, Microsoft inked highly desirable exclusive deals with OEMs and _that_, not Windows, like the clever deal with IBM about exclusivity and PC-DOS that allowed the clone industry to exist, was key to their position in the market now.

      Very little changed.

      If Linux is ever to get the dominance Microsoft enjoys today, the key is not R&D but the relationship with OEMs and software makers.

    10. Re:What FOSS can learn from MS? by TapeCutter · · Score: 1

      If you want to make money, ignoring 80% of your potential market is irrational.

      If you want a hobby that pays for itself, rationality doesn't come into it.

      --
      And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
    11. Re:What FOSS can learn from MS? by strabes · · Score: 1

      touché

      --
      Its = possessive. It's = "it is"
    12. Re:What FOSS can learn from MS? by RiotingPacifist · · Score: 1

      why would you want a market leading OS when you can have a technologically leading OS?
      Only the big companies want market share, the linus(es) and jwz(s?) just want to make the best OS that can be made, who cares if anybody uses it?!

      So what could FOSS learn? Nothing! what could OSS learn? maybe

      --
      IranAir Flight 655 never forget!
    13. Re:What FOSS can learn from MS? by gr8scot · · Score: 1

      Linux is for the "non-conformists" who want to seem smart, or for those who don't want to pay for an OS. In which category do you place Microsoft's Hotmail servers & the Akamai servers that hold Windows Updates? Don't you wish now you had known what you were talking about then?
      --
      All 19 hijackers were known terrorists 09-10-2001. Lack of FBI intelligence does not justify warrantless wiretaps..
    14. Re:What FOSS can learn from MS? by dfetter · · Score: 1

      Re: your signature, please to note that "power" is not the same as "government power," and that moving power to the private sector does not change the corruption problem for the better. In fact, it moves the corruption from a place where there are at least in theory checks and balances in place to one where only market forces, which have a lousy track record on this kind of thing, apply.

      --
      What part of "A well regulated militia" do you not understand?
  4. I would be careful by hax0r_this · · Score: 3, Funny

    .. about learning anything from Microsoft. They're probably just going to sue you for it.

    1. Re:I would be careful by MightyMartian · · Score: 4, Informative

      I see no reason to believe Microsoft on OOXML. Besides, it's a shitty, unimplementable format.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
  5. Close... by Bluewraith · · Score: 0

    "Overall, we've learned and continue to learn from open source development principles. These are making their way into the mindset, development practices, and ultimately into the products we bring to market."
    They may have learned a few key points about open source and its effectiveness, but they are leaving out one important part. The OPEN SOURCE.
    Then again, I'm not too sure if I would even want to look at their source codes.

    1. Re:Close... by plague3106 · · Score: 1, Insightful

      They may have learned a few key points about open source and its effectiveness, but they are leaving out one important part. The OPEN SOURCE.

      Maybe the open source part really isn't the important part of building good open source software? The open part gets you developers that work mostly for free, but MS already has plenty of developers, so opening doesn't benefit them.

    2. Re:Close... by debatem1 · · Score: 3, Insightful

      Not all developers can contribute equal value to your project, however. One of the big benefits to open source is that your developer base and your user base coincide a lot more. I wouldn't care to estimate the odds that if one customer wants a feature badly enough to code it, somebody else wants it badly enough to switch to your product for it, but they seem pretty good for something that's free.

    3. Re:Close... by plague3106 · · Score: 0

      Not all developers can contribute equal value to your project, however.

      That's the same regardless of open or closed source.

      One of the big benefits to open source is that your developer base and your user base coincide a lot more.

      I would say that's a net negative. You end up with software geared toward other software devleopers, not typical home users.

      I wouldn't care to estimate the odds that if one customer wants a feature badly enough to code it, somebody else wants it badly enough to switch to your product for it, but they seem pretty good for something that's free.

      I would think very low. You also make the assumption that closed source vendors aren't deliverying what their customers want. I don't think that's true, as there are lots of vendors out there and they'd be out of business.

    4. Re:Close... by Anonymous Coward · · Score: 0
      I would say that's a net negative. You end up with software geared toward other software devleopers, not typical home users. not true. with FOSS there can exist more than one fork of the code that can still remain compatible with one another [ubuntu, linux mint and debian for example] which compete with each other without being completely different beasts all together. forks that listen to their users more tend to grow over time, forks that don't die off or at the least lose users. eg. debian as an example, very good distro once you get the hang of it but ubuntu being based off debian goes in a diffeent direction, more user friendly and look what it has done for them. they now make up about 1/3 of all linux distro users easily overtaking debian its self. there are already new forks of even ubuntu that have a lot of promise which may in time replace ubuntu as the favorite. that's how it goes with FOSS. now look at the proprietary OSes like Mac or Windows: you can't fork them, there is only one major up to date version that you're pretty much stuck with. if you don't like where the development is heading, you can't really do anything about it other than switch to a completely different OS that likely has compatibility problems with software you used before. heck there are combatibility problems between windows OSes that you can not really solve because of the fact you don't have access to any of the source code. you can't optimize or strip out anything, you can't do a lot of things because of even as simple as it says you can't under the EULA. everything about it is anti-user, pro-software company.

      I wouldn't care to estimate the odds that if one customer wants a feature badly enough to code it, somebody else wants it badly enough to switch to your product for it, but they seem pretty good for something that's free. I would think very low. You also make the assumption that closed source vendors aren't deliverying what their customers want. I don't think that's true, as there are lots of vendors out there and they'd be out of business.
      like I said before, a lot of it has to do with software. if a game works on windows, it WILL NOT WORK ON ANY OTHER PLATFORM. it doesn't matter whether or not windows sucks, you can't just move anywhere else if you still want your software to work and that's the point. it's not competing on quality, it's vender lock in. software is written for windows because it is the dominant OS platform and it is dominance is closely tied to the fact that it is the defacto OS. don't believe me? go into any store you like, whether it be bestbuy, circuit city etc. and find one piece of software written to be usable on anything other than windows. not 10, not 5 just one and see how far you get.
    5. Re:Close... by Anonymous Coward · · Score: 0

      They may have learned a few key points about open source and its effectiveness, but they are leaving out one important part. The OPEN SOURCE.
      Interestingly, there are a number of 'internal open source' initiatives at microsoft- technologies and toolsets that we're free to adopt, adapt, improve, and build upon. I 'own' one such technology here, in the sense that I'm responsible for working with contributors, developing new features, reviewing changes, and ensuring that the quality bar is high. I work with a lot of different groups who use 'our' code, anybody with the right NDA can view and modify. This development model represents a pretty significant sea-change in the working culture here, and I think it's a mistake to underestimate the signifigance of it. That you're hearing rhetoric out of the suit's heads that doesn't equate open source with the devil and communism means leadership has noticed how successful our internal open-sourcing has been in terms of engineering and quality. We're moving in that direction.
      I know, it's not the same thing- but if you had a multi-bazillion-dollar revenue stream based on selling software, would you at least think twice about handing out source if you hadn't already? These things take time.
    6. Re:Close... by debatem1 · · Score: 1

      Your argument is predicated on the idea that your end user is not a developer. In many of the areas that open source shines, there is at least significant overlap between those groups. To say, for instance, that getting code as feedback for a project like GCC is a 'net negative' would be quite foolish, ditto for projects like Apache or Emacs. Of course, developers need desktops too, but the success of OSS in developing desktop software has been somewhat more limited than in the more technical communities, doubtless at least in part to the perceived weakness you point out, so in that case I would say you may be right.

      As for the assumption that "closed source vendors aren't delivering what their customers want", I'm sorry to disappoint you, but the fact is that they aren't. That doesn't in any way diminish the fact that open source vendors aren't either, but if everybody was absolutely hunky-dory with every piece of software on the market, nobody would sell anything and we'd all get to find new jobs. The software market, however, is far from placidly sterile, with fiercely competitive entities (both closed and open) fighting for users and market share. In large part, it will be the group that delivers the most and most relevant features who will 'win' in such environments, and that means that having this kind of feedback can be the difference between a successful company or project, and a chapter 11 filing or 404 page. Again, I hesitate to speculate, but the odds that what one customer wants another one does too seem pretty good to me. The fact that the first one wanted it badly enough to write the code for it, or to hire somebody to write the code for it, is a even stronger indication that there is a need for software that does that.

      Speaking to the point about not all developers being equal, I think you may have misunderstood. My point was that code that comes from people using the software is more likely to reflect the needs of people who use the software than code that comes down from on high. Obviously, many development teams are required to go through exhaustive testing processes before their software is allowed out into the wider world, but lets face it- startlingly few developers in corporate programming actually use the code they write. That's a problem, and it's not one that's going to be solved by any specific remedy I can think of, otherwise I'd be in Monte Carlo sipping a drink and being fawned over by skinny brainless women instead of writing this little diatribe.

      All I'm saying is that OSS seems to be on to something when it comes to certain types of development. It is definitely working, and I can tell you that most of the people I do business with don't give a tinker's damn what the initial cost of their software is if it doesn't save them money down the road. There is a compelling argument to be made for code as feedback, and for the competitiveness of software developed by its own end users. What remains to be seen now is whether the OSS community can withstand the inevitable uptick of consumers who are not developers that have come with its incursions into desktop software.

    7. Re:Close... by plague3106 · · Score: 1

      Your argument is predicated on the idea that your end user is not a developer. In many of the areas that open source shines, there is at least significant overlap between those groups. To say, for instance, that getting code as feedback for a project like GCC is a 'net negative' would be quite foolish, ditto for projects like Apache or Emacs. Of course, developers need desktops too, but the success of OSS in developing desktop software has been somewhat more limited than in the more technical communities, doubtless at least in part to the perceived weakness you point out, so in that case I would say you may be right.

      But for the mast majority of software, the group of users and the subset of that group which are developers are a very high ration. GCC has a limited audience; accounting software is not so limited. Video editing software isn't either.

      As for the assumption that "closed source vendors aren't delivering what their customers want", I'm sorry to disappoint you, but the fact is that they aren't. That doesn't in any way diminish the fact that open source vendors aren't either, but if everybody was absolutely hunky-dory with every piece of software on the market, nobody would sell anything and we'd all get to find new jobs. The software market, however, is far from placidly sterile, with fiercely competitive entities (both closed and open) fighting for users and market share. In large part, it will be the group that delivers the most and most relevant features who will 'win' in such environments, and that means that having this kind of feedback can be the difference between a successful company or project, and a chapter 11 filing or 404 page. Again, I hesitate to speculate, but the odds that what one customer wants another one does too seem pretty good to me. The fact that the first one wanted it badly enough to write the code for it, or to hire somebody to write the code for it, is a even stronger indication that there is a need for software that does that.

      The proof that closed source IS developing what users want is the fact that businesses making closed source are still around. Your assertation is based on nothing but your opinion. But please, feel free to point me to something that is proof of your point.

      Speaking to the point about not all developers being equal, I think you may have misunderstood. My point was that code that comes from people using the software is more likely to reflect the needs of people who use the software than code that comes down from on high. Obviously, many development teams are required to go through exhaustive testing processes before their software is allowed out into the wider world, but lets face it- startlingly few developers in corporate programming actually use the code they write. That's a problem, and it's not one that's going to be solved by any specific remedy I can think of, otherwise I'd be in Monte Carlo sipping a drink and being fawned over by skinny brainless women instead of writing this little diatribe.

      Developers don't need to use the software. There's another group of people that have the business knowledge and DO use the software that know. They can relay this to developers. Or are you suggesting that a worker on an assembly line in an auto manufacturing plant builds the car "better" because they drive cars? I think not.

      All I'm saying is that OSS seems to be on to something when it comes to certain types of development. It is definitely working, and I can tell you that most of the people I do business with don't give a tinker's damn what the initial cost of their software is if it doesn't save them money down the road. There is a compelling argument to be made for code as feedback, and for the competitiveness of software developed by its own end users. What remains to be seen now is whether the OSS community can withstand the inevitable uptick of consumers who are not developers that have come with its incursions into desktop software.

      Of course you can make software if developers work for free. Those making the most significant changes are likely paid to work on OSS all day. Those that provide direction most certainly are paid to write the software. But they get free help from the outside.

    8. Re:Close... by debatem1 · · Score: 1

      Frankly, you aren't illustrating a superb grasp of the realities of either open or closed source development, or the businesses that survive on those models.
      I will presume that my lack of eloquence is the reason that you failed to grasp the first point, because it is very simple: the OSS model is good at some things. The closed source model is good at others. One of the places where open source has demonstrated the most significant advantages over closed source is where the developer and user base ARE closely aligned. That is all.
      As for your second point, it's just plain illogical. A company exists therefore its customers must be happy with its products- obviously and flatly untrue, and, if I may, any level of experience in the software industry would enlighten you to that fact.
      Furthermore, your point that developers are akin to production line workers (which is certainly not the case in all but the largest software shops) ignores the reality that it takes experience at more than one level of your organization to make it effective. It seems significant to me that the portions of the software industry that have the highest levels of bottom-to-top experience are the ones that have the highest customer satisfaction.
      As for your last statement, you are partially correct, though I hope you'll forgive my ignorance when I say that I don't see what that has to do with the point you quoted. Many top developers are paid by someone to write code for OSS projects, but you are incorrect when you presume that the controller of the code is paying their salaries. Usually it is third parties dependent upon the software ecosystem; the example of the relationship between the Linux kernel and the paid developers at Red Hat and Canonical comes to mind. That is the illustrative dynamic here- that a free and open project is created, then becomes commercially successful, rather than the relatively recent trend of companies buzzwording their source in an effort to get free development help. Again, however, I fail to see the relevance of that comment to my point about code as feedback.

    9. Re:Close... by plague3106 · · Score: 1

      Frankly, you aren't illustrating a superb grasp of the realities of either open or closed source development, or the businesses that survive on those models.
      I will presume that my lack of eloquence is the reason that you failed to grasp the first point, because it is very simple: the OSS model is good at some things. The closed source model is good at others. One of the places where open source has demonstrated the most significant advantages over closed source is where the developer and user base ARE closely aligned. That is all.


      Frankly, you're a pompus ass. Stop with your thinly veiled insults. No one said that for a small number of cases OSS can work better. That's not the point of the thread, its whether or not the it ALWAYS does so, and whether or not closed source can match it in those few cases.

      As for your second point, it's just plain illogical. A company exists therefore its customers must be happy with its products- obviously and flatly untrue, and, if I may, any level of experience in the software industry would enlighten you to that fact.

      If you had any experience at all in the business world, you'd see that companies that do not deliver what their customers want go out of business, except monopolies. But please, point out ten or so software companies where none of the customers are happy with the product yet buy it anyway.

      Furthermore, your point that developers are akin to production line workers (which is certainly not the case in all but the largest software shops) ignores the reality that it takes experience at more than one level of your organization to make it effective. It seems significant to me that the portions of the software industry that have the highest levels of bottom-to-top experience are the ones that have the highest customer satisfaction.

      Well, according to you, small closed source software companies don't exist because they aren't giving their customers what they want. For some reason, you seem to think its not possible for a closed souce shop to deliver customer satisfaction. Or are you changing your mind here?

      As for your last statement, you are partially correct, though I hope you'll forgive my ignorance when I say that I don't see what that has to do with the point you quoted. Many top developers are paid by someone to write code for OSS projects, but you are incorrect when you presume that the controller of the code is paying their salaries.

      While Linus may enjoy being paid to do pretty much whatever he wants for Linux, most OSS developers (those paid to work on OSS) aren't in this boat. OSS developers that moonlight are paid largely by closed source shops.

      As for your last statement, you are partially correct, though I hope you'll forgive my ignorance when I say that I don't see what that has to do with the point you quoted. Many top developers are paid by someone to write code for OSS projects, but you are incorrect when you presume that the controller of the code is paying their salaries.

      You point to the brightest light as your example. However, most OSS projects never achive the level of where someone is paid to work on them. And if you think that RedHat isn't directing the developers it has, you're sadly mistaken.

      As to your point, sorry that you seem to be verrying off to some other direction. My point was that for most software, the OSS model will fail. The fact that it can work (and not demonstratably better than the closed source model) is pretty irrelevent.

    10. Re:Close... by debatem1 · · Score: 1

      My point was that for most software, the OSS model will fail. The fact that it can work (and not demonstratably better than the closed source model) is pretty irrelevent.

      This is your problem. Had you simply stated that this was your point all along, instead of pretending to be part of a reasonable discussion, we could have been done with this much more quickly. OSS has proven that it can at least enter most markets. The question of whether it can dominate those whose developer and user bases are disjoint has yet to be settled. Saying anything more -or less- is simply irrational.

    11. Re:Close... by plague3106 · · Score: 1

      Sorry, its not my fault you didn't comprehend it. Especially since you jumped in to my reply to another poster. I have been rational this whole time, until you started with the insults.

      For about eight years now I've been hearing "this is the year of linux on the desktop." It hasn't happened. I even gave up on it, and found that commercial software DOES meet my needs better than the OSS camp. I suspect there are many out there in a similar spot. I can't imagine the typical home user though, if it wasn't sutiable for me.

      But please, tell me how we will know when the question is settled? What is your criteria? What makes you think it hasn't already been settled?

    12. Re:Close... by debatem1 · · Score: 1

      I'm not your strawman, so put down the torch. I don't think this is the year of the Linux desktop, and have been quite explicit in saying that I think that OSS is very good at some things, while closed source models seem to do better at others. I think that many Linux desktop applications are at or approaching the point of competitiveness with their closed-source brethren, but I also think that its going to be a long time before some parts of the industry come under contention.
      My initial question was simply whether OSS will wind up dominating arenas with disjoint user and developer bases the way that it does where those two groups are closely aligned, and you ask when we'll know the answer to that. My general feeling is that we already know that it is possible for projects like Firefox to contest some segments of the market, but that we probably won't see just one model in very many parts of the industry unless an application that simply obliterates its competition winds up emerging, and I don't think its possible to predict whether such a rogue entity would be open or closed.
      You ask what my standards for making that judgment would be, and if you're driving at the point that its a subjective estimation, you're right. Market position is very difficult to correctly ascertain, and I don't particularly think its the kind of thing either of us really wants to spend our lives doing. As a result, I hope you'll forgive me when I borrow the words of Anthony Comstock and give you the deeply unsatisfying answer that "I'll know it when I see it".
      As far as it not having been settled, well, we're sitting here arguing about it. Sure, I'm writing this from a Linux machine running Firefox, but from your earlier statements I envision you doing the same from a Windows box and IE. With any luck, competition will help to improve the quality of all the contenders.
      If you don't mind, I'd like to hear more about your experience with open source. What projects did you think were most or least competitive?

    13. Re:Close... by plague3106 · · Score: 1

      I'm not your strawman, so put down the torch. I don't think this is the year of the Linux desktop, and have been quite explicit in saying that I think that OSS is very good at some things, while closed source models seem to do better at others.

      Which was totally irrelevant to my comments meant for the OP.

      I think that many Linux desktop applications are at or approaching the point of competitiveness with their closed-source brethren, but I also think that its going to be a long time before some parts of the industry come under contention.

      Do you run Linux on your desktop? I've found this to be patently false.

      My initial question was simply whether OSS will wind up dominating arenas with disjoint user and developer bases the way that it does where those two groups are closely aligned, and you ask when we'll know the answer to that. My general feeling is that we already know that it is possible for projects like Firefox to contest some segments of the market, but that we probably won't see just one model in very many parts of the industry unless an application that simply obliterates its competition winds up emerging, and I don't think its possible to predict whether such a rogue entity would be open or closed.
      You ask what my standards for making that judgment would be, and if you're driving at the point that its a subjective estimation, you're right.


      Part of my point is that the FF team has a big player backing them with money. Should that company no longer fund the primary developers, would FF survive? I don't really think so. GNUCash is a more appropriate model; the developers think I want all the gory details of double entry accounting, which I don't. Things like MS Money or Quicken hide those details for me. GNUCash also was lacking in any reporting of any kind. They even admit it: "I'd guess that GnuCash's biggest problem is that programmers don't use the software." These are the majority of OSS projects.

      You ask what my standards for making that judgment would be, and if you're driving at the point that its a subjective estimation, you're right. Market position is very difficult to correctly ascertain, and I don't particularly think its the kind of thing either of us really wants to spend our lives doing. As a result, I hope you'll forgive me when I borrow the words of Anthony Comstock and give you the deeply unsatisfying answer that "I'll know it when I see it".

      Well, the problem is that without objective qualifications we can't really ever evaluate if your statement is true.

      As far as it not having been settled, well, we're sitting here arguing about it.

      Well, I imagine we could forever too, since we don't have anything objective to go on.

      Sure, I'm writing this from a Linux machine running Firefox, but from your earlier statements I envision you doing the same from a Windows box and IE. With any luck, competition will help to improve the quality of all the contenders.

      Windows and FF actually, although I am using IE about the same as FF now that IE7 is out.

      If you don't mind, I'd like to hear more about your experience with open source. What projects did you think were most or least competitive?

      It was harder to use. GNUcash wasn't cutting it (no reports), I still had random crashes. The documentation is non-existent in most cases, and managing my network is easier with Windows Server 2003 (SBS). And of course RPM hell. I felt like I was spending more time fighting to get Linux to do what I want than actually having it do what I wanted. And I put the time in too; I had run a linux server for 10 years and on the desktop for three. It was honestly more frustrating than Windows.

    14. Re:Close... by debatem1 · · Score: 1

      Do you run Linux on your desktop? I've found this to be patently false. Yes, I do- and more importantly, on my clients' desktops, since a major part of my job is windows to Linux migrations and the accompanying training. We consistently find that after an acclimation period productivity sits right about where it did before. It sounds like you had a bad experience, and as a developer I really am sorry about that, but it doesn't parallel what our clients find or we wouldn't be in business.

      Part of my point is that the FF team has a big player backing them with money. Should that company no longer fund the primary developers, would FF survive? Would the project continue? Yes. Would it have anywhere near the market share it does? No. But the amount of cash involved has nothing to do with whether a project is open source or not.

      GNUCash is a more appropriate model; the developers think I want all the gory details of double entry accounting, which I don't. Things like MS Money or Quicken hide those details for me. GNUCash also was lacking in any reporting of any kind. They even admit it: "I'd guess that GnuCash's biggest problem is that programmers don't use the software." These are the majority of OSS projects. Again, I'm sorry to hear that you had a bad experience, but part of what I was saying earlier is the fact that the vast majority of software is bad software, open or closed source. For every bad open source program that you point out, I can point out a bad closed source program, and we're back to the "my anecdote is better than your anecdote" game. In the absence of data, we are just opining.

      Well, the problem is that without objective qualifications we can't really ever evaluate if your statement is true. As I've tried to carefully explain *we*have*no*data*. All we have are perceptions and opinions. I, naturally, think my opinion is correct; that the open source model provides specific advantages, that much open source software is of high quality and that it is in many respects a level playing field, with the leaders in some market segments being closed source and the leaders in others being open. You, naturally, think yours is correct, and while I disagree with it, that fact doesn't make it any more or less valid.

      Well, I imagine we could forever too, since we don't have anything objective to go on. Given the level of sarcasm, I presume you have a nice simple 10-or-so word definition of 'good software' that I can whip up a test for and be done? I didn't think so. People who live in glass houses...

      It was harder to use. GNUcash wasn't cutting it (no reports), I still had random crashes. The documentation is non-existent in most cases, and managing my network is easier with Windows Server 2003 (SBS). And of course RPM hell. I felt like I was spending more time fighting to get Linux to do what I want than actually having it do what I wanted. And I put the time in too; I had run a linux server for 10 years and on the desktop for three. It was honestly more frustrating than Windows. I'm not sure about GNUcash, as I don't use it (we have an accountant for that) but I'm amazed that you had so much difficulty with the desktop, given that level of experience with Linux. We get individuals who have no technical background to the point where IT calls are down to normal within a few days, and with one major exception have never had a persistent problem. Any issues in particular? How long ago was this?
    15. Re:Close... by plague3106 · · Score: 1

      Yes, I do- and more importantly, on my clients' desktops, since a major part of my job is windows to Linux migrations and the accompanying training. We consistently find that after an acclimation period productivity sits right about where it did before. It sounds like you had a bad experience, and as a developer I really am sorry about that, but it doesn't parallel what our clients find or we wouldn't be in business.

      Well, you're giving them training. Are you also taking over managing the servers from then on? As I attempted to be a self taught admin (somewhat) sometimes I didn't care about the details of why something worked, I just wanted it to work. I can dig into the whys later. I found on Linux, I had to spend an inornate amount of time to figure out it, and the why details usually drowned out the how.

      Which is why I don't think OSS will get anywhere; someone HAS to be trained, they can't just sit down with very basic knowledge and off they go. In a business setting, you usually have IT to call on to answer questions. Home users don't, and they sometimes find certain tasks in Windows hard to do. Imagine home users now trying to muddle through Linux.

      Would the project continue? Yes. Would it have anywhere near the market share it does? No. But the amount of cash involved has nothing to do with whether a project is open source or not.

      If the project continues, and statistically speaking no one is using it, does it matter? There's no competition at that point.

      Again, I'm sorry to hear that you had a bad experience, but part of what I was saying earlier is the fact that the vast majority of software is bad software, open or closed source.

      I'm not disputing that there's plenty of bad software on either side. However, on the closed source side there's enough good software that I can do what I want without much hassle. Part of the problem on the open side is that you can't even tell WHAT the good software is. Its much more of a hassle to even install the application, so I was much less included to looking much. If it didn't have an RPM, I pretty much gave up after a while. Even then there were issues; when MSN and Yahoo where locking out 3rd party IM applications, I had to upgrade Kopete quite a bit. But the RPMs were so far behind, and when they finally came out, I pretty much had to update the ENTIRE KDE system.. which of course falied horribly. Again, can you imagine a home user with these problems?

      As I've tried to carefully explain *we*have*no*data*. All we have are perceptions and opinions. I, naturally, think my opinion is correct; that the open source model provides specific advantages, that much open source software is of high quality and that it is in many respects a level playing field, with the leaders in some market segments being closed source and the leaders in others being open. You, naturally, think yours is correct, and while I disagree with it, that fact doesn't make it any more or less valid.

      The only data I have is that so far we haven't had the Year of Linux on the desktop, nor is it looking any better. I think those OEMs that sell both Linux and Windows still have a majority of Windows, and I'm not sure any of them said Linux is rising in any significant way. I realize this isn't a perfect metric, but its the best one I think we have for now.

      Given the level of sarcasm, I presume you have a nice simple 10-or-so word definition of 'good software' that I can whip up a test for and be done? I didn't think so. People who live in glass houses...

      Huh? I'm not being sarcastic at all; just stating that we seem to have moved into an area that is subjective.

      I'm not sure about GNUcash, as I don't use it (we have an accountant for that) but I'm amazed that you had so much difficulty with the desktop, given that level of experience with Linux. We get individuals who have no technical background to the point where IT calls are down to normal within a few days, and with one major e

    16. Re:Close... by debatem1 · · Score: 1

      Well, you're giving them training. Are you also taking over managing the servers from then on? As I attempted to be a self taught admin (somewhat) sometimes I didn't care about the details of why something worked, I just wanted it to work. I can dig into the whys later. I found on Linux, I had to spend an inornate amount of time to figure out it, and the why details usually drowned out the how.

      We do give them training, but we don't take over management, preferring instead to offer break-n-bake support plans and service guarantees. We do both desktops and servers, and training for both IT staff and end users. We find that end users typically cause no more problems on Linux than they do on Windows after an adjustment period, and depending on the setup, sometimes less. IT is always a hassle, but that's just the nature of the beast- people do not like retraining away from a skill set that they have based their careers around.
      You are correct that Linux as a server OS does not encourage you to perform operations you do not fully understand. Linux on the desktop, I think we may have to agree to disagree. My personal experience (no more or less valid as evidence than your experiences, of course) is that we have few problems with desktop installs, and that what problems we have usually come down to unsupported hardware (industrial controls, etc), and even that has become quite infrequent now. To the best of my knowledge, we haven't had any major complaints about the (admittedly limited) applications we install.

      Which is why I don't think OSS will get anywhere; someone HAS to be trained, they can't just sit down with very basic knowledge and off they go. In a business setting, you usually have IT to call on to answer questions. Home users don't, and they sometimes find certain tasks in Windows hard to do. Imagine home users now trying to muddle through Linux.

      Again, I think we may have to agree to disagree. I don't think that very many people would have argued with you a few years ago- I know I wouldn't have- but I also think that OSS has come a long way since then. Of course, at this point we are using OSS as a synonym for Linux, which I in particular ought to know better than to do, but I hope you'll understand if I use it as shorthand where I don't otherwise elaborate.
      My personal experience (again, not valid data) is not broadly representative. It is based on our service to a region that is both desperately poor and possessed of an educational system that would shame Somalia. Most of our end users treat computers as bewildering, terrifying, and capricious lesser gods, whose power to help you is only exceeded by its ability and desire to do you harm. They have little Windows experience, and have never heard of Linux or, indeed, an operating system, before. They don't understand, and don't care, as long as it keeps the gray box happy. We have little difficulty in training them to do basic office and worksite tasks on Linux, and life goes on. Our more experienced Windows users are another story. They do not like to retrain, and frequently try to treat Linux as "Windows for cheapskates". They run everything as root to avoid the inconvenience of passwords, they complain bitterly that things are not in exactly the same place "as they used to be", and they generally experience higher levels of frustration and greater difficulties than the above mentioned group, even if they do not do significantly more with those machines. I suppose you can turn that into an argument for Windows- that people are already trained on it and do not need retraining- but while that makes a good business case I don't think it addresses the fundamental question we're talking about, which seems to be the quality of the software in question.

      If the project continues, and statistically speaking no one is using it, does it matter? There's no competition at that point.

      I think I wasn't as clear as I wanted to be. When I say competitive, I mean feature-for-featu

    17. Re:Close... by plague3106 · · Score: 1

      Well.. these posts are getting a bit long for me. :-)

      I understand your experience differs, and that's fine as you said. However, a couple of things. Did you learn much of what you needed for Linux because you have a job doing so? I'm certainly not afraid of Linux by any means. Its just that its more difficult to learn. I do fine with shells and what not, after all I used Unix all through my five year college program. That's when I first came into contact with Linux as well. "Unix on my PC, awesome!" But a normal user won't be able to just sit down and be able to muddle their way through. If I had a hard time, I don't think a home user on their own would do much better.

      Your user experience is limited (it seems) to business users. That's fine as I said, but I don't think that the experience a business user of linux (who likely doesn't manage the computer they use in any way) translates to a home user well (because they have to "manage" the system themselves).

      In that sense, market share IS important, because home users also add hardware to their PC. You can't just buy anything and assume it will work on Linux.

      As far as /home being on an NFS mount; I think that was recommended when I first setup my server. At any rate, the idea was to keep user data on the server. I understand WHY everything locked up, but it didn't lead to a great experience. Contrast this to Windows; a few group policy settings (which affect more than the location of user documents) and user files and settings are stored on the server. With Windows, its smart enough to use the local store and sync later. No configuration needed.

      Regarding the "security implications" arguement, I fail to see why advanced or dangerous options should be "hard" to do or only done through a text editor. When setting a group policy setting, there are warnings if need be on the page where I sent the option, and there's always an Explain tab, which details all options and what they mean. Help on Linux sucks. Man pages tell you an option, but rarely do more than say "enables or disables the option." There is MUCH better documentation on Windows than Linux.. and that's sad. Back to the "for experts by experts," well, it really sucks if you're just beginning and need to get something done. In Windows, I can be handheld until I learn more about what I need to do.. then I can do it using another tool or diving into the registry or what have you. With Linux, it was like "you can't do that until you're an expert." So.. how do I learn if I can't get started? That attitude needs to go..remember, I am a developer, and I have done some Linux and Windows administration (I even did a sort of a minor in systems admin which covered both.. and Linux was easier because I had already started learning it years before on my own).

      I know I've moved to Linux, but the problem is worse with other OS software. A few projects have enough attention that they are good quality. Most (like GNUCash) don't have that. Quality may be there, but usability won't be. Or usability will be there, but quality won't. Or you just flat can't get the software installed. The OS software you've been pointing to are exceptions, not the rule, at least that's what I've found. There is something to be said for being able to go to BestBuy or Amazon and see the software I want there; at the very least, I know a good number of people are using it. With many OS applications, that metric is missing.

      I appreciate the offer to help with Kopete, but the problems were a few years ago now. I went back to Windows full time in 06. I'm happy, Windows does what I want, and contrary to other posters here is reliable. As for the printer, I don't think that's ever been addressed. Notice one of the "helpful" posts is to throw the machine way and buy an HP.

      I understand you like Ubuntu, but that's part of my skeptism now. First it was Slack, then

    18. Re:Close... by debatem1 · · Score: 1

      I understand your experience differs, and that's fine as you said. However, a couple of things. Did you learn much of what you needed for Linux because you have a job doing so? I'm certainly not afraid of Linux by any means. Its just that its more difficult to learn. I do fine with shells and what not, after all I used Unix all through my five year college program. That's when I first came into contact with Linux as well. "Unix on my PC, awesome!"

      My areas of interest in computing are supercomputing, CPR, and (more recently) virtualization. Windows does not give me the kind of power as a developer that I need to pursue my research in those areas. After a brief flirtation with Solaris when I was in high school (the school had a Sun server), I moved to Linux full time and haven't looked back.

      Your user experience is limited (it seems) to business users. That's fine as I said, but I don't think that the experience a business user of linux (who likely doesn't manage the computer they use in any way) translates to a home user well (because they have to "manage" the system themselves).

      We set up all kinds of systems, in all kinds of offices (including home offices), but most of them are not centrally managed, and in many of them- especially former Mac shops- the users have a tremendous degree of latitude in what they do and how they do it. You are absolutely right that the comparison between a large corporate desktop and a standard home machine is pretty much apples and oranges, but our installs on a lot of machines are basically stock Ubuntu, Mint, or (if requested) Fedora. Nobody seems to have a big problem, and in fact many people only notice that the background has changed and that the start button is in a different place. After that, most don't *seem* to care, although of course they know me as 'the Linux guy', and people aren't usually in a hurry to criticize others' livelihoods. Again, however, I have no data with which to back up my claims, so it could just be my admittedly biased perception.

      In that sense, market share IS important, because home users also add hardware to their PC. You can't just buy anything and assume it will work on Linux.

      The only devices I've had real problems with on Linux- besides really strange things like one-off industrial controllers- are blackberries. They really just don't work the way they're supposed to, although the Barry project tries really hard. Besides that, most hardware does work now, and again, I have nothing but anecdotes to hand you.

      As far as /home being on an NFS mount; I think that was recommended when I first setup my server. At any rate, the idea was to keep user data on the server. I understand WHY everything locked up, but it didn't lead to a great experience. Contrast this to Windows; a few group policy settings (which affect more than the location of user documents) and user files and settings are stored on the server. With Windows, its smart enough to use the local store and sync later. No configuration needed.

      Well, its not the lockout issues I was commenting on so much as security, since /home is frequently scanned by UID 0 processes and UID 0 access is badly handled by NFS, leading to serious security issues- but then I'm the guy who includes TEMPEST scanning as part of a security audit. The better solution would probably have been SSHFS overmounting a known safe /home on the local machine. It probably would have spared you a lot of headaches and would definitely have been more secure. It is also *far* easier to set up, since it requires less in the way of cooperation from your server. Another possible route (and much more comparable to Windows' group policy) would have been rsync, which is quite easy to set up.
      You've said several times now that you think that Windows is easier to use than Linux. I don't think that's correct at very many levels of user experience, but again, we're throwing anecdotes

    19. Re:Close... by plague3106 · · Score: 1

      My areas of interest in computing are supercomputing, CPR, and (more recently) virtualization. Windows does not give me the kind of power as a developer that I need to pursue my research in those areas. After a brief flirtation with Solaris when I was in high school (the school had a Sun server), I moved to Linux full time and haven't looked back.

      So you've never really used Windows then (the NT line.. 2000 or higher)? I've found lots of people say Windows is for morons or its overly simply. The fact is that it's complex, and much of the complexity is hidden. But its there if you really need to dig in. Given that I've seen many comments about virtualization and supercomputing that mirror yours, I'm not suprised that Windows doesn't fit your needs. I would check back now and then though (maybe now, because Server 2008 is out), because MS is trying to move into these areas. I've found that they usually succeed; not on the first or second attempts, but they have a good record. I know.. that's not what most /.ers will say.

      We set up all kinds of systems, in all kinds of offices (including home offices), but most of them are not centrally managed, and in many of them- especially former Mac shops- the users have a tremendous degree of latitude in what they do and how they do it. You are absolutely right that the comparison between a large corporate desktop and a standard home machine is pretty much apples and oranges, but our installs on a lot of machines are basically stock Ubuntu, Mint, or (if requested) Fedora. Nobody seems to have a big problem, and in fact many people only notice that the background has changed and that the start button is in a different place. After that, most don't *seem* to care, although of course they know me as 'the Linux guy', and people aren't usually in a hurry to criticize others' livelihoods. Again, however, I have no data with which to back up my claims, so it could just be my admittedly biased perception.

      Fair enough. I never had any kind of training on Linux. A bit of "training" on Unix and the Unix philosophy in college though. At first I liked the unix philosophy. But for some reason that seems to translate into "make console app, if you want a UI, build a UI that calls the console app and parses it's output." Yuck. Good Windows develops actually do have a similar philosophy, but they'll build a library and a console app or UI will use the same library. Larger OSS projects do this as well.. but I found many of the other OSS apps didn't.

      Maybe my problem was that I was inbetween a "real" systems admin and home user. Neither expert nor dummy.

      The only devices I've had real problems with on Linux- besides really strange things like one-off industrial controllers- are blackberries. They really just don't work the way they're supposed to, although the Barry project tries really hard. Besides that, most hardware does work now, and again, I have nothing but anecdotes to hand you.

      Fair enough; we're both going off anecdote at this point. I have seen that wireless is still a bit crap shoot as are printers. Not that printing is wonder in XP, although Vista seems to work flawlessly. I haven't had any printer problems in Vista.

      Well, its not the lockout issues I was commenting on so much as security, since /home is frequently scanned by UID 0 processes and UID 0 access is badly handled by NFS, leading to serious security issues- but then I'm the guy who includes TEMPEST scanning as part of a security audit. The better solution would probably have been SSHFS overmounting a known safe /home on the local machine. It probably would have spared you a lot of headaches and would definitely have been more secure. It is also *far* easier to set up, since it requires less in the way of cooperation from your server. Another possible route (and much more comparable to Windows' group policy) would have been rsync, which is quite easy to set up.

      Ahh. Well I was

    20. Re:Close... by debatem1 · · Score: 1

      So you've never really used Windows then (the NT line.. 2000 or higher)? I've found lots of people say Windows is for morons or its overly simply. The fact is that it's complex, and much of the complexity is hidden. But its there if you really need to dig in. Given that I've seen many comments about virtualization and supercomputing that mirror yours, I'm not suprised that Windows doesn't fit your needs. I would check back now and then though (maybe now, because Server 2008 is out), because MS is trying to move into these areas. I've found that they usually succeed; not on the first or second attempts, but they have a good record. I know.. that's not what most /.ers will say.

      No, I've used Windows extensively. First, my high school days aren't all that far behind me, and XP was already out. Second, as part of my business- many legacy business apps cannot be ported without monumental effort, and so it is frequently the case that we set up a Windows box with a Linux passthrough.
      As for Windows supercomputing, I wish them great good luck but don't see it happening, as the UNIX world's tools for HPC etc are just incredible. It would take a LONG time and a lot of money to come up with a comparable feature set.

      Well, you've probably had much more time. All of my Linux experience was me, all by myself, trying to be inbetween. Wanting to administer my own network like an expert would, yet not having the resources provided if I worked with Linux all day. Again, maybe you're right about home users, and my experience is because I'm in this weird limbo. As far as making unsafe options available, well, we're not talking about a gun, so lets not go down that route. You can reformat a machine that gets owned, you can't bring someone back from the dead. Also, if the option is adequately explained and the security implications are stated, I don't see what the problem is. In the end, you can set that unsafe option on either system. The problem with Linux seems to be they are just hiding it, so if you find the option you may be less aware of the implications. Windows points it out, saying "hey, this could be really bad, here's why, but if you want, go for it." As someone trying to learn more about administring systems, I find that is more helpful.

      Its all there, it just happens to be in either the man files or the ultimate documentation. Once you learn how to use a command's basic invocation (from irc or wherever), then check the man pages for reference documentation, and you're generally fine. Again, all of this is anecdotal- my experience is x, yours is y, ergo, we run around in circles, but like I say, between talking directly with the developers, reading the man pages, and, if you're really masochistic, perusing the source code, you'll figure it out. In the end, there's really nothing in Linux that's totally opaque, which is, once again, a major advantage for those willing to take advantage of it.
      As far as security is concerned, we probably don't want to get into that flamewar, but there are a lot of things you can do to a system that simply can't be undone. If your customer database gets cracked, its game over. If someone installs a malicious utility, its game over. God forbid they be able to insert a kernel module. The assumption that box security is more important that infrastructure or data security is one of the major problems with home use security models, and really highlights a major difference in approach between Windows and Linux. It doesn't help that much of security research is very convoluted stuff, and that many elements of a security strategy cannot be considered in isolation. So, I can't really agree that every insecure option should be just as easily available as any given security-neutral option, any more than I think that every option available on the CLI needs to be available in the GUI.

      Your suggestion is to send out configuration files via rsync? Fair enough. Seems like this should be made easier to do tho

    21. Re:Close... by plague3106 · · Score: 1

      No, I've used Windows extensively. First, my high school days aren't all that far behind me, and XP was already out. Second, as part of my business- many legacy business apps cannot be ported without monumental effort, and so it is frequently the case that we set up a Windows box with a Linux passthrough.

      Heh. I get the impression you're a bit younger than me. I graduated college from a five year program before XP came out (only by months though). I've been using computers since MS-DOS 3.1 was the latest version.

      As for Windows supercomputing, I wish them great good luck but don't see it happening, as the UNIX world's tools for HPC etc are just incredible. It would take a LONG time and a lot of money to come up with a comparable feature set.

      I wouldn't underestimate MS. Many now defuct companies did.

      Its all there, it just happens to be in either the man files or the ultimate documentation. Once you learn how to use a command's basic invocation (from irc or wherever), then check the man pages for reference documentation, and you're generally fine. Again, all of this is anecdotal- my experience is x, yours is y, ergo, we run around in circles, but like I say, between talking directly with the developers, reading the man pages, and, if you're really masochistic, perusing the source code, you'll figure it out. In the end, there's really nothing in Linux that's totally opaque, which is, once again, a major advantage for those willing to take advantage of it.

      This is mostly what I've been saying. I know I could eventually get what I need, but in today's computers and GUI applications, if I need to go as far as going to the source, the application has failed from a usability standpoint. That's my issue, and it's likely an issue for many others.

      As far as security is concerned, we probably don't want to get into that flamewar, but there are a lot of things you can do to a system that simply can't be undone. If your customer database gets cracked, its game over. If someone installs a malicious utility, its game over. God forbid they be able to insert a kernel module. The assumption that box security is more important that infrastructure or data security is one of the major problems with home use security models, and really highlights a major difference in approach between Windows and Linux. It doesn't help that much of security research is very convoluted stuff, and that many elements of a security strategy cannot be considered in isolation. So, I can't really agree that every insecure option should be just as easily available as any given security-neutral option, any more than I think that every option available on the CLI needs to be available in the GUI.

      I'm not trying to get into a flamewar either; I never said box security was more important that network security. I said that the options, which may be dangerous, are still accessable and that adequate warnings and explainations are given. Right there, in the dialog to set the option (or by pressing F1). I found that in Linux, I would find the option, but the various settings of that option aren't adequately explained where you set the option. You need to go digging. Again, it's a usablity failure.

      Set up /home the way you want it, both on the server and on the desktop. Then set up a cron job to rsync it every X interval (turns out its 30 minutes to 2 hours for Group Policy Objects). There is a convenient GUI tool called Unison that does this for you. As for figuring out what files to sync, just do a server->client sync of anything in /home that starts with ., and everything in /etc. Then do a client->server sync of everything else in /home if you want to share those files. Since rsync uses SSH as a carrier protocol, it is quite secure. Again, all of this can be done in Unison, although I am personally more comfortable working with rsync itself.

      Again, quite a lot

    22. Re:Close... by debatem1 · · Score: 1

      This is mostly what I've been saying. I know I could eventually get what I need, but in today's computers and GUI applications, if I need to go as far as going to the source, the application has failed from a usability standpoint. That's my issue, and it's likely an issue for many others.

      Depends on what you mean by 'usability'. End users should never have to go further than the forums or IRC. Administrators should never have to go further than the man pages. Developers should be looking at either API documentation or source, and preferably both. All of the above are addressed in a good program, and most of the *major* projects do so. You've already said that you're not really a fan of the major avenue of assistance in Linux, which is the community forums and IRC, and I guess if that's how you feel about it that's the way it is, but I don't think that without community assistance you're comparing apples to apples in terms of support.

      I said that the options, which may be dangerous, are still accessable and that adequate warnings and explainations are given. Right there, in the dialog to set the option (or by pressing F1). I found that in Linux, I would find the option, but the various settings of that option aren't adequately explained where you set the option. You need to go digging. Again, it's a usablity failure.

      I'm not sure if there's a particular piece of software than you're referring to here, but most man pages seem exhaustively complete to me, especially on major projects. /shrug.

      Again, quite a lot of steps. Does Unison setup both client and servers? When building a new workstation do I need to use Unison to configure the client again, or is there a way to say "this server controls your settings" and leave it at that? I'm not sure I would have ever found or heard of Unison if not for this discussion... which again I think points to a problem.

      If you already have rsync and ssh on your server, you just need to install Unison on the client, tell it which directories to sync which way (can be saved in a config file, which can also be shared safely) and point it at your server.

      As for not having heard of it without my help, well- yeah. That's why the community exists. That's what I mean by living documentation. If you ask somebody a question- and we're easy to find- we'll answer if we can, and know where to look if we can't.

      Hmm... options can be good and bad. In this case, I lean toward bad, because I now have to evaluate one of these packages before I can even start administering my network. If I choose poorly, I have to undo everything and switch to another package.

      Hmmm. I'm afraid I don't agree with you here- I tend to believe that competition in a market segment tends to improve the quality of the competitors and increase the power of the consumer- but I guess to each their own.

      No, my knowledge of it was that it is a scripting language (at least, when I first heard of it, it was) and I try to stear clear of those. Maybe it's changed, or maybe I'm confusing it with TCL/TK. I dunno, it's been a while. I tend to stick to languages that are similar to C / C++ sytax. I don't know why, but I've always liked it more than Basic, and other languages just haven't appealed to me as much. Not that I haven't used a few, at least a couple of times each.. lisp, snobol, eiffel, VAX assembly and some other's I'm forgetting. :-)

      It's a scripting language in the same sense as lisp is- interpreted, quick to write, blurs the line between data and code- but it's pretty common for a lot of general purpose programming anymore. A lot of the syntax is pretty much C++ sans punctuation, which I find handy, but I figured since you mentioned both .NET and Java that I would mention Python since the three major implementations of Python are C, .NET CLR, and Java.

      By the way, I'm not continuing to post to cha

    23. Re:Close... by plague3106 · · Score: 1

      Depends on what you mean by 'usability'. End users should never have to go further than the forums or IRC. Administrators should never have to go further than the man pages. Developers should be looking at either API documentation or source, and preferably both. All of the above are addressed in a good program, and most of the *major* projects do so. You've already said that you're not really a fan of the major avenue of assistance in Linux, which is the community forums and IRC, and I guess if that's how you feel about it that's the way it is, but I don't think that without community assistance you're comparing apples to apples in terms of support.

      Well, I guess that's where our limits differ. I think end users shouldn't need to leave the application at all. Ideally, they can sit down and figure it out because the UI is intuitive. At worse, they should have to look at the help file or other assistence the program offers. Admins should have the same for their configuration tools. Developers shouldn't need to go to the source, but given how curious we are it can be helpful if they can, although I've been doing fine so far.

      I'm not sure if there's a particular piece of software than you're referring to here, but most man pages seem exhaustively complete to me, especially on major projects. /shrug.

      There was some DVD burning software, some BT clients, GNUCash springs to mind again. Even some things in the WM were lacking; some features of KDE were very well documented, other's had nothing.

      As for not having heard of it without my help, well- yeah. That's why the community exists. That's what I mean by living documentation. If you ask somebody a question- and we're easy to find- we'll answer if we can, and know where to look if we can't.

      Again this is part of our differing views. The community doesn't always have answers, or I have to wait (I did the forum thing, never IRC). These things require time though, which I have limited amounts of to spend on various tasks. As to finding software.. where does one go to ask which software will fill a certain need?

      Hmmm. I'm afraid I don't agree with you here- I tend to believe that competition in a market segment tends to improve the quality of the competitors and increase the power of the consumer- but I guess to each their own.

      It can increase the power of the consumer, if the consumer can invest time into evaluating. I tend to allot more time to evaluating something based on its cost to me.. in the case of OSS (or any software, really) if I can't sit down and in a few minutes start doing what I need or want to, I move on. On the OSS side, there were too many things to "move on to" so it became frustrating.

      It's a scripting language in the same sense as lisp is- interpreted, quick to write, blurs the line between data and code- but it's pretty common for a lot of general purpose programming anymore. A lot of the syntax is pretty much C++ sans punctuation, which I find handy, but I figured since you mentioned both .NET and Java that I would mention Python since the three major implementations of Python are C, .NET CLR, and Java.

      Hmm, didn't know Java had a Python implementation. Pretty cool. I heard IronPython is pretty impressive actually.

      We do have different views, but I don't see that as a problem. Do I think that GUIs are inherently less powerful than CLIs are? Absolutely, and any sys admin worth their shell scripts knows the same thing. Does that mean they do not have a place? Absolutely not, since any UI designer worth his pixels knows that most users are terrified of the terminal. Again, I think we're going in circles on this man pages issue, and I'm not going to spend much more time addressing it, but I think that they're usually perfectly fine as reference material and as a supplement to online help, and I think we can agree to disagree on that.

      I agree that CLIs can be more powerful. I th

  6. Star Trek analogy by Tibor+the+Hun · · Score: 3, Insightful

    -Microsoft Cube is hailing us, Captain!
    -Bring it up on the main screen. ...
    We are Microsoft. Resistance is futile. Prepare to be Embraced.

    --
    If you don't know what AltaVista is (was), get off my lawn.
    1. Re:Star Trek analogy by zotz · · Score: 1

      "I see a red door and I want it painted black."

      Take on of your mother's little helpers. Fix ya right up.

      all the best,

      drew

      --
      FreeMusicPush If you want to see more Free Music made, listen to Free
  7. Open source development principles? by Spinlock_1977 · · Score: 5, Insightful

    ...open source development principles?

    What are those, exactly? I'll bet he couldn't name them. I'll bet no one can. It's a bazaar, not a cathedral!

    --
    - The Kessel run is for nerf herders. I can circumnavigate the entire Central Finite Curve in a lot less than 12 parse
    1. Re:Open source development principles? by VGPowerlord · · Score: 1

      Maybe they just want to create a bizarre cathedral?

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
  8. While they are at it. by jameskojiro · · Score: 2, Funny

    Maybe they will release more specs to their API so we can make our own damn Windows OS, with hookers and blackjack, forget the hookers and and backjack, forget the whole damned thing!

    --
    Tsukasa: All I really want, is to be left alone...
  9. Lessons Learned by thomas.galvin · · Score: 5, Funny

    Open standards, choice of platform, no vendor lock-in, release-early-release-often, user-modifiable programs, ability to fork... yeah, they've learned all kinds of stuff from Open Source.

  10. what microsoft can learn from open source by OrochimaruVoldemort · · Score: 1

    always allow community modding, never lock up the source code, make applications on all platforms.

    --
    If people can get past, can they get future? Best way to confuse a stoner
    1. Re:what microsoft can learn from open source by jo42 · · Score: 1

      You forgot "be able to download the source|binaries|ISOs and run it for free".

  11. Re:Windows has always been influenced by competiti by Volante3192 · · Score: 0, Troll

    Did it hurt when your soul got sucked out?

    Just curious, cause there's this Aston Martin I've had my eye on...

  12. Ramji doesn't understand a thing. by morgan_greywolf · · Score: 5, Interesting
    Oh, look! It's Sam Ramji, showing he knows nothing about open source principles.

    Modular architectures
    You can find these wherever you see participation at scale - and often a rearchitecture to a more modular system precedes expanded participation. Great examples of this are Firefox, OpenOffice, and X11 - from both the historical rearchitecture and the increased participation that resulted. The Apache HTTP server and APR are good examples that have been modular for as long as I can recall. OpenOffice? Modular? Maybe OOo is developed in a modular way, but the end result is hardly anything but modular. In fact, it's quite monolithic -- when you start OpenOffice Writer, you also start OpenOffice Calc, Base, Draw, Impress, etc.

    Programming language agnostic
    A given project uses a consistent language, but there are no rules on what languages are in scope or out of scope. Being open to more languages means opportunity to attract more developers - the diversity of PHP/Perl/Python/Java has been a core driver in the success of a number of projects including Linux. Open source projects are 'programming language agnostic' because they used public, published and open interfaces. They follow standards. The reason a the Linux kernel build process can be a mixture of bash, Python, Perl, awk, etc. is that all of these things can connect together using pipes and whatnot. The reason you can write GNOME applications in almost any programming language is that the APIs are completely open. The reason why AbiWord and KWord can read Open Document Text files is that that spec is completely open and free of royalties, patents, etc.

    Feedback-driven development
    The "power user" as product manager is a powerful shift in how to build and tune software - and this class of users includes developers who are not committing code back, but instead submitting CRs and defects - resulting in a product that better fits its end users. Huh? How are CRs the same as accepting code patches? Open Source development differs in that these "power users" as he calls them can make their own changes and, if necessary, fork off their project to offer a competing or even a completely different project.

    Built-for-purpose systems
    frequently seen in applications of Linux, the ability to build a system that has just what is needed to fulfill its role and nothing else (think of highly customizable distributions like Gentoo or BusyBox, as well as fully custom deployments). Uhhhh....BusyBox is not a "distribution" and cannot really be compared to Gentoo except that, yes, the program (as in single program, hence, not a distribution) is cutomizable through the use of custom build options.

    Sysadmins who write code
    ability of a skilled system administrator to write the "last mile" code means that they can make a technology work in their particular environment efficiently and often provide good feedback to developers. This is so fundamental to Unix and Linux environments that most sysadmins are competent programmers. Unix sysadmins are generally NOT competent programmers. We're lazy schmucks who whip up quick-and-dirty scripts to accomplish tedious and boring tasks out of sheer laziness. And then we call it 'enhancing productivity' in an attempt to get a raise. :)

    Standards-based communication
    Whether the standard is something from the IETF or W3C, or simply the implementation code itself, where these are used projects are more successful (think of Asterisk and IAX2) and attract a larger ecosystem of software around them. Real open standards are developed by the community at large through agreement, not by a monopoly who can change the "standard" at anytime without notice.
    1. Re:Ramji doesn't understand a thing. by Crispy+Critters · · Score: 1
      "Oh, look! It's Sam Ramji, showing he knows nothing about open source principles."

      He seems to be conflating open source principles and the Unix philosophy. Perhaps a principle of open source would be, um, opening the source.

    2. Re:Ramji doesn't understand a thing. by HermMunster · · Score: 1

      Your comments are very educational. I would ask that you please not feed the Vole. We don't want to educate them. Let them falter and fall on their own. Why put more money into the hands of an abusive convicted monopolist? Don't put any more money in their hands by telling them where they are wrong. Sometimes it is just best to not say anything and let them falter and fall. They certainly won't point out what you don't understand, based on those same principles. They won't educate you, at least not for free, so don't feed the Vole.

      --
      You can lead a man with reason but you can't make him think.
    3. Re:Ramji doesn't understand a thing. by kimvette · · Score: 1

      The reason why AbiWord and KWord can read Open Document Text files is that that spec is completely open and free of royalties, patents, etc.


      Oh sure they are, until some douchebag patents the prior art and it gets rubber-stamped by the USPTO.
      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    4. Re:Ramji doesn't understand a thing. by Anonymous Coward · · Score: 0

      The "Vole"? Seriously? WTF is wrong with you people? I love free software, but every day I realize more and more that the "community" is just broken beyond repair.

    5. Re:Ramji doesn't understand a thing. by the_womble · · Score: 1

      I am fairly sure the term "Vole" for MS did not originate with free software advocates, but on a IT news site, most of whose journalists are Windows users.

      It may sem a triviality, but the point is that a lot of Windows users dislike MS too, they just do not know enough about alternatives to jump ship: they have lots of misconceptions about it and think it is only for Unix geeks.

  13. What Open Source Can Learn From Microsoft by Anonymous Coward · · Score: 3, Interesting

    Hmm interesting...

    If you just say it's great you can get more of the market.

    If you say you innovate people believe you.

    If you name your product close to the more popular true standard you can confuse the PHBs into paying you money instead.

    If the competition is winning tell everyone your competitor is unfair to competition.

    If people like a bad practice, and it's yours, then keep doing it.

    There more money in prolonging the problem then just putting out a solution.

    If you can convince a big bux company to buy your product it is a good vehicle for the advertising/PR department.

    No mater how much you neglect your customers' previous purchases, privacy and security, you can still keep them buying your products.

  14. oh lordy by pak9rabid · · Score: 1

    what open source can learn from Microsoft You mean like how to rush stuff to market? Or perhaps how to copy features (poorly) from successful competing products and patent as your own? Or maybe you mean how to publish an API in which you promise not to sue people for utilizing it, only to stab your users in the back as soon as they make something better than you (that's soon to come down the pipe I'm sure)? I've said it once and I'll say it a million times. Fuck off Microsoft. The world doesn't need you. Sooner or later the rest of the world will realize that and throw you away like a parking ticket.
  15. Software Engineering 101? by 140Mandak262Jamuna · · Score: 5, Interesting
    What the article lists as "lessons to be learned from Open Source" is what is usually taught in Software Engineering 101. Come on, Modular Architecture, language agnostic coding, follow standards... This is the lesson from Open Source? These are basic things that every software manager should know.

    The problem with MSFT is not that they don't know these things. They do. But the internal power structure in MSFT is so driven by "if the playing field is level, we will lose" cowards. So they still do things that was ok when they held a 20% share against Word Perfect and 10% (by revenue) share against unix and mainframe giants, back in the late 80 and early 90s. They got lots of money and grew too fat and have too many layers of management. So they go and hire this dogbert to tell them what they already know.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  16. When did Linux stop being "cancer" & "communis by christian.einfeldt · · Score: 0, Troll

    I hope the first thing that Microsoft learns is that we in the FOSS community are not stupid, and we remember being called "cancer" and "communists". I personally will welcome Microsoft when they GPL Microsoft Windows and Microsoft Office. Until then, I am inclined to believe that it is just preparation for more "extend, embrace, and extinguish."

    Sam offered to come speak at our local LUG, and we turned him down, because we didn't think that he had anything of relevance to say to us. So be advised, Microsoft is sending Sam out on a tour to make nicey with the FOSS communities. But until they GPL Microsoft Windows and Microsoft Office, it is still all part of "extend, embrace and extinguish" the cancerous commies.

  17. Sticking feathers up your butt... by jhRisk · · Score: 2, Funny

    ...does not make you a chicken.

    Tyler Durden (1999)

    --
    That's just my POV... no more, no less.
    1. Re:Sticking feathers up your butt... by imipak · · Score: 4, Funny

      Well thanks, you just ruined my weekend.

  18. Open Source has Learned From Microsoft by HermMunster · · Score: 5, Insightful

    Open Source has learned how a company can abuse their position, how a company can be a monopoly and make billions and then influence those who are elected into office to protect us. Those billions go a long way to influencing the lawmakers to push aside any attempt to make a better cheaper product.

    It is ludicrous to think that a product that can be made cheaper and better should be put asunder because some powerful monopoly can influence the powers that be. There's no socialistic tendencies there. No communistic tendencies. It is pure capitalism that is being thwarted by Microsoft's practices. Microsoft is a bully, an entity that has one goal and that is to rake in all the money while destroying the competition and they are doing that with their monopoly.

    Your privacy is being violated hundreds of millions of times a day by Microsoft with WGA/WGN and Vista's equivalent. They are able to get away with it because they don't take competition seriously because they don't have to. Would you go out and pay $2000 for a TV from Best Buy and then allow Best Buy to enter your home to verify that you didn't actually receive stolen property? What if they want to do that every week or every month (inspect your home for stolen goods)? What if they say that they'll do this with a hidden camera? Would you permit it? Say you buy frequently form Walmart. Would you permit Walmart to enter your home to inspect your property to prove you didn't steal it from the store? I think not. You wouldn't let your neighbor enter your home upon accusations that you stole something from him. You wouldn't let the police enter your home even if the neighbor filed a complaint.

    What the open source community practices has learned is that Microsoft is the type of entity that uses "Embrace, Extend, Extinguish" tactic to kill solid technology and those companies trying to bring them to market. The open source community has learned that Microsoft has threatened every Linux user with 235 alleged patents claiming everyone will have a price to pay to Microsoft, without Microsoft stating specifically what is being violated. This is like an oil company stating that they are going to sue car owners for using gasoline from one of their competitors because their competitor may have allegedly use some of the IP in the gas refining process. Then they threaten the car manufacturers or large companies that use that same gasoline with lawsuits if they don't stop using the competitors gasoline. Then they refuse to say which competitors and they refuse to say which IP has been violated. BTW, that IP was probably stolen by them to begin with.

    We've learned from Microsoft that they will steal IP from small entities and when caught will ignore those companies request to have Microsoft pay up. Z4 Technologies is one of those companies. In this case Microsoft was contacted about their use of the IP developed by this firm for the purpose of over the internet product activation. According to the final ruling which went in favor of Z4 Microsoft knew they were in violation of the IP of Z4 and they continued to use it. During the trial they flooded the court and Z4 with paperwork in hopes of covering it up. The day before the trial began Z4 found the evidence. Z4 won the trial and were granted approximately $100 million. In the ruling the Judge noted numerous acts of misconduct on Microsoft's part and though he could have awarded 3 times the amount he only awarded an additional $25 million in special damages (which is no small amount by any measure). The Judge also noted that Microsoft had participated in these acts because they believe that Z4 was to small and to weak to defend their own IP. Upon appeal Microsoft lost with the Judge also noting the numerous acts of misconduct. With the latest appeal of this Microsoft lost that as well with all awards in tact.

    But what you must understand from this is that Microsoft stole the IP of Z4 which Microsoft used to keep you from stealing their IP. So, they stole the technology

    --
    You can lead a man with reason but you can't make him think.
    1. Re:Open Source has Learned From Microsoft by Anonymous Coward · · Score: 0
      Once again, I am writing in response to Mr. HermMunster's offhand remarks, and once again, I merely wish to point out that HermMunster's deputies, who are legion, must be exposed and neutralized wherever they lurk. Here's my side of the story: HermMunster is still going around insisting that his ideologies are good for the environment, human rights, and baby seals. Jeez, I thought I had made it perfectly clear to him that the ostensible basis for his speech codes is as phony as the loose and biased standards applied to enforce them. That conclusion is not based on some sort of abusive, unruly philosophy or on HermMunster-style mental masturbation, but on widely known and proven principles of science. These principles explain that HermMunster's pusillanimous attempt to construct a creative response to my previous letter was absolutely pitiful. Really, HermMunster, stringing together a bunch of solecistic insults and seemingly random babble is hardly effective. It simply proves beyond a shadow of a doubt that he holds onto power like the eunuch mandarins of the Forbidden City -- sterile obstacles to progress who turn once-flourishing neighborhoods into zones of violence, decay, and moral disregard.

      I disapprove of defeatism and I disapprove of HermMunster's ill-bred agendas. HermMunster may mean well but he plans to vandalize our neighborhoods. He has instructed his comrades not to discuss this or even admit to his plan's existence. Obviously, HermMunster knows he has something to hide. If he gets his way, I might very well go crazy. HermMunster wants to sell quack pharmaceutical supplies (and you should be suspicious whenever you hear such tell-tale words and phrases as "breakthrough", "miracle", "secret remedy", "exclusive", and "clinical studies prove that..."). Why he wants that, I don't know, but that's what he wants.

      I could accuse HermMunster of using brusque ivory-tower academics to get his way but I wouldn't stoop to that level. Yes, I realize that he interprets his easy meanness as unselfish philanthropy, but for the sake of brevity I've had to express myself in simplified terms. He insists that he has a duty to conceal the facts and lie to the rest of us, under oath if necessary, perjuring himself to help disseminate the True Faith of Bulverism. Sorry, HermMunster, but, with apologies to Gershwin, "it ain't necessarily so." My argument is that he is the devil incarnate. Ridiculous? Not so. I will stop at nothing to unmask his true face and intentions in regard to expansionism. My resolve cannot fully be articulated but it is unyielding. As evidence, consider that HermMunster's functionaries get a thrill out of protesting. They have no idea what causes they're fighting for or against. For them, going down to the local protest, carrying a sign, hanging out with HermMunster, and meeting some other dysfunctional sewer rats is merely a social event. They're not even aware that HermMunster says that he can override nature. This is at best wrong. At worst, it is a lie.

    2. Re:Open Source has Learned From Microsoft by cp.tar · · Score: 1

      Whatever!

      First I used Hotmail and the Linux dudes told me BSD was evil.

      Sorry, that was a typo.

      BSD is a devil.

      --
      Ignore this signature. By order.
    3. Re:Open Source has Learned From Microsoft by HermMunster · · Score: 1

      Lol, dude. You have a document created that you simply just do a search and replace of the name and then paste that into the reply section of the sites you visit?

      Of course, none of it makes sense. It reminds me of when the weak AI programs were released in the early 80s where you would enter a question into a command line DOS program that program would respond with something that seemed to make sense. I remember buddies stating that if you couldn't tell it wasn't a human it was real AI. Anyone with a little spare time could query enough to realize it wasn't a human.

      Are you human?

      --
      You can lead a man with reason but you can't make him think.
    4. Re:Open Source has Learned From Microsoft by Anonymous Coward · · Score: 0

      "It is pure capitalism that is being thwarted by Microsoft's practices"

      Pure capitalism is a fantasy, lets face this, it doesn't exist. This idea that microsoft is not capitalistic is insane, influencing government is just another market force, just like piracy and the black market is another market force. The whole basis of capitalism is based on individualism, greed and self-interest, just how exactly is microsoft NOT being self-interested? This idea that 'pure capitalism' apart from personal greed and all the failings of human beings is bullshit, idealogy is bullshit in general - all that exists in the real world are transactions and relationships between people based on what they believe to be x, or not x, whatever something is x or y is quite irrelevant since it's socially constructed, there is no ideal capitalism just like there is no ideal model for socialism, communism, etc, in an ever changing world no economic idealogical model really describes the underlying social reality.

      People behave in ways that protect their interests and income streams, that's how real markets work in practice. Market idealists like Milton friedman, et, al are a cooky insane bunch divorced from the real world. All human beings no matter what COLOR (capitalism, communism, socialism) they like to dress up their behaviour as or not as, is pure hyperbole

  19. 'what Open Source can learn from Microsoft' by milsoRgen · · Score: 1

    More games.

    Build it and they will come...

    --
    I'm sick of following my dreams. I'm just going to ask where they're goin' and hook up with 'em later.
    1. Re:'what Open Source can learn from Microsoft' by Vexorian · · Score: 1

      You know, this is what annoys me the most, the assumption (made by some gamers) that PC games are really an important reason not to switch from windows, I like games too, but get some facts straight, around PC users gamers are the minority, among PC gamers, casual gamers are the majority, which means that other OSes already got tons of options for the majority of PC gamers. More: Most gamers do not use the PC as a gaming platform, and while we are on it, the current most popular commercial game got a Mac version and has had an amazing record on successful WINE experiences. Fun?

      --

      Copyright infringement is "piracy" in the same way DRM is "consumer rape"
    2. Re:'what Open Source can learn from Microsoft' by milsoRgen · · Score: 1
      I scoff at your comment, nay I spit at it.
      What do you define a casual gamer? If by casual you mean the cubicle worker playing solitaire then yes I dare say you are right and I dare say they are in the majority. However if by casual gamer you mean one that plays computer implementations of licensed board games, Civ class stategy or classic arcade ports... The gamer willing to spend the odd 10, 20 maybe even 40 dollars. Which is what I consider casual gaming... Well then you are just up shit creek with out a paddle, me and my brethren prefer to buy our games with proper licensed IP and an expectation of customer support. I wish I could offer some numbers, but I'm willing to bet the percentage of gamers that buy the odd 10-20 dollar game that runs on the Windows OS far exceed all Linux users outside of a commercial/business enviroment. Of course that is just my guess, I have no numbers. But from my personal experiance, I have found the number one reason people will not let me install a distro is the lack of games. People aren't stupid, well they are but not in ways we might expect. They want to be able to go buy a 10 dollar Deer Hunter install at Wal-Mart... And theres a reason why deer hunter installs on Windows and not Linux... And that reason can be argued till we are both blue in the face, the fact of the matter the people who buy boxed retail games are so far in the majority your little comment shows how far detached you are reality.

      Windows=Games
      Games=Enthusiasts
      Enthusiasts=Recommendations
      Recommendations=Sales

      More: Most gamers do not use the PC as a gaming platform Well I guess if you buy into what the console makers spew forth as marketing data, and it may as well be correct. But once again we are forgetting, what constitutes a 'gamer'?

      the current most popular commercial game got a Mac version and has had an amazing record on successful WINE experiences. I'm going to assume since you're not specifying the game in question you are referring to World of Warcraft... And does that not bother that you must emulate the Windows API to play on Linux? that's hilarious that your one glorious example is a windows game with mac support that happens to run on Linux via WINE to do an enthusiastic community.

      I'm sorry but true enthusiasts require full acceleration. And we enthusiasts spend the dollars on the gear, the gear that we recommend to friends and family down the line... The sooner open source projects (which I know and love) can find a way to implement the latest and greatest hardware the sooner Open Source can be recommend by us users that use our machines as an entertainment device.


      And further more I am drunk, I never post on Slashdot while drunk, but your comment, with a 2 modifier struck me as so ignorant and misguided I had to respond... So pick apart what I have said if you will, I'll beer bong some coffee and respond in kind.
      --
      I'm sick of following my dreams. I'm just going to ask where they're goin' and hook up with 'em later.
  20. Re:The soul is a religious concept by Anonymous Coward · · Score: 0

    Nice of you to join us Steve Ballmer.

  21. Translation: by Anonymous Coward · · Score: 0

    "We're stealing more open-source code to put into Windows because our programmers don't know shit about OS design."

  22. Cue Henry Spencer quote by DrYak · · Score: 5, Informative

    yeah, they've learned all kinds of stuff from Open Source.


    As Henry Spencer has said (and also as quoted by some commentators on the original page) :

    Those who do not understand Unix are condemned to reinvent it, poorly.


    Microsoft just fails to understand what actually makes the success of Linux and F/LOSS, and thus they are only ble to pull out pale copy of what they think they've seen in order to fill such PR announcements.

    ----

    As an example, their entry about "Modular architectures" is almost funny if not tragic, citing OpenOffice.org and Mozilla Firefox as examples (which are actually criticized by the Linux community sometimes for being too bloated). What makes *nices systems cool isn't the ability to stuff plugins into big apps, what makes them cool is the "Unix way" : programs that just do 1 thing but do it well. Modularity is about all these small single-function programs and all those libraries (for ex.: pattern finding, on-the-fly compression, conversion filters, multimedia processing, etc) that can be freely played with by the user and assembled into more complex never-intended-for-this-usage construction, which forms the basis for huge application like those cited above. Application like VLC aren't an example of modularity, but an example of what modularity enables by putting together a bunch of functions already provided by libraries.

    Also the ultimate advantage of F/LOSS is about freedom and the feeling that the software you have belongs to you. Something that is completely un-achievable with Microsoft style softwares.
    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Cue Henry Spencer quote by kmike · · Score: 2, Interesting

      Their goal isn't to copy F/LOSS or the principles of open source movement,but to influence the general public (or at least those pointy-haired guys in charge) so it will associate MS products with Open Source and openness in general. This rhetoric does just that, nothing more, nothing less.

      The recent "opening" of some of MS protocols and specifications blends well into this PR strategy.

    2. Re:Cue Henry Spencer quote by bigstrat2003 · · Score: 0, Flamebait

      Also the ultimate advantage of F/LOSS is about freedom and the feeling that the software you have belongs to you. Something that is completely un-achievable with Microsoft style softwares. If that were the ultimate advantage, OSS would have a grim future indeed. The ultimate advantage (or disadvantage, depending on the program) is the quality of the software, not some ideology. Period. Unless you prefer to not actually use your software, I guess.
      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    3. Re:Cue Henry Spencer quote by argiedot · · Score: 1

      You seem to be having trouble understanding: The freedom to change the code is a feature, and allows you to actually use your software.

    4. Re:Cue Henry Spencer quote by bigstrat2003 · · Score: 2, Insightful
      So, you're saying that all this time, open source proponents didn't know it was possible to use software they couldn't see the source to? Well, in that case...

      REJOICE, MY GEEK BROTHERS! YOU NEED NO LONGER FEAR CLOSED SOURCE! IT WILL NOT REFUSE TO WORK FOR YOU MERELY BECAUSE YOU CAN'T SEE THE SOURCE CODE!

      Come on now. The freedom to change the code is in no way a feature of the software. It's entirely separate from the software, and if my software isn't doing what I need it to do, it doesn't matter whether the source is closed or open. That software sucks for my purposes, open or closed.

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    5. Re:Cue Henry Spencer quote by Anonymous Coward · · Score: 0

      The freedom to change the code is in no way a feature of the software. The definition of word "feature" is quite blurred in common usage and changes from person to person there is no point fighting over it ..

      if my software isn't doing what I need it to do, it doesn't matter whether the source is closed or open. That software sucks for my purposes, open or closed. Relationship with a software is just like with your girlfriend.. it is usually more complicated than just "this whole software sucks" and "this software rocks". Many times it is like .. "Wow.. that software has awesome concept.. but the way they implemented this is bad.. It does not seem to work for our organization. If only I had the source, I could have given it to my nephew who is a programmer and he would have customized it for me. Now because it comes from [a large company] and is closed source, I will have to beg them for source and shell out XYZ million/thousands of dollars. Pathetic how the software could have been useful to us otherwise.." . Or if you are a programmer.. "Kick ass CD album software.. cool.. but it's re-indexing and sorting is so slow.. it took 45 seconds to sort and index 3000 song records. My hospital data management software has cool algorithms.. it sorts and re-indexes a whole table of 20 thousand complicated records in under 7 seconds, and our server's h/w config is the same as your desktop. Let us check what my algorithms can do to your software.." Now that you have got the basic lessons on Free and Open Source Software, go think about it.
  23. I'm going to respectfully disagree with that. by Mongoose+Disciple · · Score: 4, Insightful

    He/they have learned something from Open Source software and principles.

    It may not have been what you wanted them to learn, though. Frankly, a Microsoft may (metaphorically) buy things at your church bake sale or play basketball with your kids, but they're never going to convert to your religion.

    1. Re:I'm going to respectfully disagree with that. by morgan_greywolf · · Score: 1

      Free and Open Source Software is NOT a religion for me. Notice I didn't use the 'Free Software' moniker or the name 'GNU/Linux' spread by the Disciples of Stallman. Not that I entirely disagree with RMS or the FSF on many principles, but I see the Free and Open Source movements as complimentary -- together they are pushing for what it is important engineering-wise (the "knowledge of the masses" or ESR's Bazaar concept from CatB), as well what is important technology policy wise -- the use of truly open standards, APIs, specifications and source code so that this technology we're creating can outlive us and successive generations. Technology needs to be transparent because no matter how you look at it, companies like Microsoft will not be here forever. Unfortunately, we're treating out data as if they will be. This is a mistake that costs industries billions every year.

      I'm a practical guy. I use what works. But I also believe that monopolistic vendor lock-in practices are undercutting society and stifling the growth of technology. It's time for these practices be put to an end. Q.E.D.

    2. Re:I'm going to respectfully disagree with that. by Mongoose+Disciple · · Score: 1

      I'd consider myself practical as well, really.

      Where we diverge is that I see the Cathedral and the Bazaar as complementary rather than antithetical, encouraging the growth of technology taken as a whole, not stifling it.

      There are kinds of software that each, in a vacuum, is good at producing, and kinds of software that they aren't good at producing. If Open Office is "good enough" for many purposes, it's because it stands on the shoulders of Cathedral giants like Office. If Windows Server 2008 is a good server OS, it's because it's learned so much about how to make a good one from Linux. (Although I'd probably pick Team Foundation Server as a much better example of what I see as a great closed source product that absolutely could not have existed without a dozen great open source projects blazing trails in different areas.)

      Some projects need a single, unifying vision or the willingness to write code that the developer doesn't personally want; some projects really need strong security or any of a hundred other things that a thousand pairs of eyes on the source provide. I think we're better for a world where both are possible.

    3. Re:I'm going to respectfully disagree with that. by Antique+Geekmeister · · Score: 2, Insightful

      It's worse: they send their kid to soccer practice with your kids, and use it to write playbooks on how to cheat for their kid's team. Look at what they did with SPF, stapling "SenderID" on top of it, breaking SPF, and taking credit for the installed SPF userbase to lend credence to their claims of anyone using SenderID.

      And take a look at Active Directory. It's builot on the open standards of Kerberos, dynamic DNS, DHCP, LDAP, and the like, all woven together and proprietized in ways that not break compatibility. This includes oddnesses done to Kerberos, which MIT sued over and for which the Kerberos patches were very quickly published by MIT to fix the compatibility breakage. It's also taken years for the Samba team to reverse engineer and make a stable Active Directory replacement service, because they're refused to publish what they "extended" onto the open standard applications.

      This behavior is one of the best reasons I can see for using GPL rather than the so-called "more free" licenses, because GPL style licenses actually protect us better from this sort of embrace and extend behavior.

      Yes, they've learned how to steal from the very best and then make it "theirs".

  24. How Interesting by jeevesbond · · Score: 2, Insightful

    As in science, this incremental improvement will move all of us forward.

    Well this is interesting, whenever Open Source tries to learn from Microsoft Steve 'rabid-monkey-man' Ballmer starts throwing around software/idea patent threats.

    If this is an incremental process that can move us all forward, how about Microsoft offer up their patents to the OSDL Patent Commons? Or just allow Free/Open Source software developers to work without threat of being sued? Oh yeah, they'd rather reserve the right to sue anyone who dares to even look at their markets.

    --
    I'm going to transform myself into a mighty hawk. Either that or I'll just go and work at Dixons, haven't decided yet.
  25. Re:When did Linux stop being "cancer" & "commu by FishWithAHammer · · Score: 1

    Sam offered to come speak at our local LUG, and we turned him down, because we didn't think that he had anything of relevance to say to us.

    Yeah, god help you listen to anyone outside the groupthink.

    Civil, open discourse on both sides can do nothing but benefit everyone. Grow up.

    --
    "You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
  26. The joke that is port25.. by comm2k · · Score: 4, Insightful
    There is no point in criticizing or making fun of this article. Just glance over what they have been doing on port25 and you'll realize that it is filled with crap like this. The SpikeSource article is a real gem:

    One of the key findings was that customers want better open source and Microsoft interoperability, and moreover, they felt this was the issue that the industry has collectively done the least to address. While there has been a lot of unfortunate history that has gotten in the way of this, ultimately customers don't care as much about grudges as they care about everything simply working. Together, SpikeSource and Microsoft's open source lab are doing something about it. Excuse me?! Apply Kirk's comment about Klingons.. thats all I can say.
    1. Re:The joke that is port25.. by MightyMartian · · Score: 2, Insightful

      It's a pretty absurd claim, considering guys like Samba and the OO.org teams have basically had to reverse engineer everything to get their software to function with Microsoft's protocols and file formats. In fact, even with Microsoft's "co-operation" there's a real tangible fear with many FOSS developers that there's poison pills all over the place.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
  27. Re:When did Linux stop being "cancer" & "commu by dedazo · · Score: 1

    until they GPL Microsoft Windows and Microsoft Office

    Besides the arrogance of using the GPL as the measuring stick (as if all the other licenses were irrelevant), if this is your threshold for acceptable action by the part of Microsoft I'd recommend just keeping up the "lalalala i can't hear you" routine. It will be much more rewarding in the long term.

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  28. Re:FOSS can learn from Microsoft by HermMunster · · Score: 3, Interesting

    Bottom line is that the OSS model will surpass the closed source model in time. It has no choice but to do that. Open cooperative community development has no choice but to meet and exceed that of the closed source model due primarily in that it is very evolutionary. The OSS industry will update faster (bug fixes and new features) than the closed source with the typical 18 month to 5 year product cycle of the closed source. Given time the OSS industry will create more useful features and modify those features over and over long before equivalent features will be available in the closed source market. It is like an organism that evolves more rapidly vs an organism that evolves in huge spurts with larger time intervals in-between. The organism with the shorter evolutionary steps has a greater possibility of finding flaws, correcting them, and creating new features and testing those.

    Open source by its very nature will overcome monolithic development cycles of closed source, given enough time. Closed source doesn't have the time and can't experiment much. Open source has all the time in the world.

    Let's also keep in mind that 1) Microsoft is a finite entity with limited number of developers and thus a limited number of ideas, where only so many of those limited ideas will pay off (this is why they steal everyone else's ideas). 2) The Open Source community has the resources of the community as it exists "world-wide" and thus has a significantly greater chance of coming up with new and unique ideas. 3) Some ideas are just obvious and that is why you see duplicity of ideas in each platform. These ideas tho can be extended and modified faster due to Open Source's ability to have more minds looking at the product and submitting coding ideas.

    If any of you read the blogs of the ex-Microsofties that left just prior to or just after the Vista release you can see clearly that each developer in the Microsoft community is a microbe that has limited access to the brain and does what they are told even if the process is to redo and undo and redo the same thing again and again. This is certain to result in significant slow downs and even failures (as we have seen with Vista).

    The Open Source model will succeed because it is designed to succeed whereas closed source practices dictated by a criminal monopolist to developers using their platform tools, etc., will result in systemic failure and their ultimate demise. How long will it take? It doesn't matter because the open source community has the time and the manpower.

    --
    You can lead a man with reason but you can't make him think.
  29. open source and MS by jriding · · Score: 1

    until MS applies for a patent on it.. the USPO approves the patent then no one can make advancements on the ideas and growth... just like Science!!!

    --
    love the taste, hate the texture
  30. Re:When did Linux stop being "cancer" & "commu by HermMunster · · Score: 3, Informative

    Microsoft used to contact companies during the 80s that were developing products. The ideas that were coming out were quite incredible. Pen computing was one of them. It was reported over and over again that Microsoft would ask for a presentation of the ideas of a given company's product and then a few months later announce that they were adding this or that feature into Windows. Why would anyone who was going after venture capital to bring a product to market survive with the dominant criminal monopolist announcing competing technologies to be incorporated into the OS? In the 80s this scenario played out endlessly.

    This is what Microsoft did to pen computing. Do we have pen computing today? No. Because Microsoft announced pen windows. Pen computing died. Then so went pen windows.

    Were some of these companies responsible for their actions? Absolutely. They helped their own demise. The lesson learned from Microsoft is not to demonstrate your product to them for they will steal the ideas, just as they are stealing the ideas of the open source community under the guise of learning from them and teaching back. Microsoft will not do anything for free.

    Apple showed Microsoft their version of the Mac prior to the official release. They wanted Microsoft to develop their word processor and spreadsheet for it. Microsoft did that, but they also took all the ideas and made Windows. When confronted Gates simply slapped Jobs in the face telling him to grow up. What was Jobs to do? His product demanded applications and Microsoft was a leading developer, even though they'd purchased their Macintosh word and excel programs from other companies.

    With open source it is still subject to the stealing of technological ideas from a closed source vendor but that's part of the benefit. Open Source benefits by the exposure of companies such as Microsoft stealing other's ideas instead of developing them themselves, which they seem nearly incapable of doing.

    Essentially, Microsoft has created over the past 2 decades the air of distrust due to outright theft and manipulative practices that ultimately were deemed illegal by the court system.

    What is best is that the open source community continue it's uninfluenced progress toward the time when all software is developed in the same manner.

    --
    You can lead a man with reason but you can't make him think.
  31. One other quote by Dr.+Manhattan · · Score: 1

    One of my .sigs, seen on Slashdot: "Choice, flexibility and cost are really the driving factors [for Linux adoption]. And Microsoft would have to stop being Microsoft to ever compete with that combination." - emkey

    --
    PHEM - party like it's 1997-2003!
  32. Re:When did Linux stop being "cancer" & "commu by Mongoose+Disciple · · Score: 1

    If we're being honest, there's a lot of "stealing" going on all over the place.

    You'd be very hard pressed to find much if anything Open Source in the extremely broad category of "things that developers don't want, on average, more than non-developers" that doesn't owe a serious debt of inspiration, if not more, to the Closed Source world. E.g. Open Office, Firefox, GIMP.

    You'd equally be very hard pressed to find much if anything in the Closed Source world produced in the last 10+ years in the broad category of "things that developers want more than non-developers" that doesn't owe a serious debt to the Open Source world. A lot more than just developer-y things, honestly, but that's where it's most prevalent/obvious.

    The ultimate result is that we can do a lot more cool things with computers now than ten years ago, and everybody wins.

  33. One thing... by zkiwi34 · · Score: 1

    If OSS is "influencing" such as the serfs who are working on Server 2008, might that not be a door or window for some lawyer to assert that Microsoft are inserting GPL code into their products? Ah, but wouldn't that law suit be "fun."

    1. Re:One thing... by Shados · · Score: 1

      They're talking about philosophy, not code :)

  34. Re:When did Linux stop being "cancer" & "commu by gujo-odori · · Score: 1

    Why is "Microsoft releasing software under the GPL (or $FREE_LICENSE, if you insist)" an unreasonable standard? Red Hat, MySQL, IBM, and Sun (just to name four; there are many others) all did/do that, and it's what put them in good standing with the FOSS community. Why should we hold Microsoft - the most egregious anti-FOSS offender - to a lesser standard than that?

  35. uh-huh by RelliK · · Score: 2

    So when is microsoft going to stop bastardizing open standards? For instance, are there any plans to finally release specifications to microsoft's proprietary extensions to Kerberos? [and I don't mean the NDA bullshit microsoft tried to pull]. Or how about the ODF vs. MS OOXML debacle?

    This is what microsoft will never "learn" because their business model depends on not learning it.

    --
    ___
    If you think big enough, you'll never have to do it.
  36. Re:When did Linux stop being "cancer" & "commu by dedazo · · Score: 1

    What is this "standard" and who established it?

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  37. Re:When did Linux stop being "cancer" & "commu by bigstrat2003 · · Score: 1

    Because it doesn't require open-sourcing their software to be a friend to open-source. Analogy: I'm not a Christian at all, but I have some very good friends who are Christians. They don't treat my friendship with suspicion because I haven't converted.

    --
    "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
  38. Re:FOSS can learn from Microsoft by xoundmind · · Score: 1

    How long will it take? It doesn't matter because the open source community has the time and the manpower.

    Quite correct.

    Oddly, this is the same strategy used by Islamic terrorists.

  39. Seriously, OSS can learn from Microsoft by ProfessionalHostage · · Score: 2, Insightful

    - Dumbification of Linux: this is being done by Ubuntu & Kubuntu. And I'm not saying this as a negative thing, entry level Linux should be easy enough for just about anyone.

    - Run a study on user-usability: OSS can hire or contract an established and well-known 'GUI usability' expert/company and let every top OSS products that directly used by the end user to consult to them.

    - Embrace .NET, and create a version that add more functionality, features and 'cool stuff' and make sure anything that written on this version wont compile out-of-the box on VS from Microsoft.

    - Ms. Exchange?

    - More GUI for everything: Stop forcing us to edit some shady configuration file.

    - Out of box Linux distro should be just like Windows': Just some basic programs (notepad, file manager, paint, etc.), but packed with more drivers for lots of stuff.

    We don't need amaroK, MPlayer, tvtime, Gimp, and KDevelop out of the box just like we don't need Winamp, VLC, AFM2000, Photoshop and Delphi on Windows. Thanks to package managers, we can just click here and there, and have them available in a couple of minutes. Not having drivers, now that's a show-stopper.

    - MSDN: Seriously.. we need MSDN-like website for Linux. Running around the web for some API, and stuff in Linux. While on the M$ side we can get everything from Win32, .NET, SQL Server, and some other Microsofties in one place (and maintained properly). ... just my $0.02 ...

    1. Re:Seriously, OSS can learn from Microsoft by Handover+Phist · · Score: 1

      - Ms. Exchange?

      I would kill to see this happen

      - MSDN: Seriously.. we need MSDN-like website for Linux. Running around the web for some API, and stuff in Linux. While on the M$ side we can get everything from Win32, .NET, SQL Server, and some other Microsofties in one place (and maintained properly)

      Sourceforge, anyone?

  40. Re:When did Linux stop being "cancer" & "commu by HermMunster · · Score: 1

    You are absolutely correct, except for your last sentence. My post described what was happening and how the abuse was causing the demise of companies with great ideas that were being brought to market. Their demise didn't help us and give us cooler things. Often the ideas were dead-ended on purpose by Microsoft. Microsoft wanted to kill Pen Computing because they were an OS other than Microsoft that was directly competing. They killed Pen to kill a competing OS. They never came out with pen windows. Today we have similar touch based OSes and the hand held market that relies on touch input but in reality that's a far cry from what Pen Computing was trying to accomplish.

    Another example of how your last sentence fails is Sun's Java and the idea of "Embrace, Extend, Extinguish". Java was a cross platform modular development system that would technically work in any OS on any browser. Back in the late 80s and early 90s there was talk that this object oriented pluggable apps would completely eliminate the need for an OS. Things could be snapped together and your services could be pick and choose. You wouldn't technically need a computer, just a dumb terminal. This was a direct threat to Microsoft's OS offerings. Microsoft responded accordingly. Even though the legal agreement between Sun and Microsoft dictated that Microsoft could not extend JAVA to be platform specific they still did it. Since Windows was the dominant OS at the time the extensions were gaining all the development attention. The cost was that the java applets were not useable on any platform other than Windows. This was completely contrary to what Sun wanted. It was part of Microsoft's "embrace, extend, extinguish" philosophy that we have all heard of. Sun sued Microsoft and Sun won. Microsoft was ordered by the court to remove the Microsoft specific Java VM from all windows installs. This is just one case where Microsoft's copying didn't benefit everyone by doing it their way. Instead we have what Sun wanted and though some debate the quality of Java others believe it is doing what it was intended. Even tho, Microsoft hasn't suffered as Java hasn't usurped the OS as they believed.

    My post did touch on the concept that some ideas are obvious and thus you can't help but influence across platforms (closed and open). A computer needs the ability to type into it. Hence the editor/word processor. It is the epitome of calculation so thus we'd expect to see spreadsheet type applications. It is capable of storing, indexing, and retrieving large amounts of data in the fraction of the time a human could do it, thus we need a database. We'd need menus, dialog boxes, the ability to move things around, sound, video, etc. All of that is obvious. How it is done and how well it is done is another matter, but the ideas are the same.

    When we consider IP lawsuits that are rife today we can see that these, in the long run, will (and do) stifle innovation, creativity and progress. A closed source company with IP hurts the industry. An open source company with IP is sort of an oxymoron (though probably not unheard of). In order to slow down and keep ideas from being "borrowed, begged, or stolen" the closed source world pushes for IP while those that are interested in just making product for everyone without (or with little cost) tend to stay away from IP. IP is being used to kill the "open". You can't be open if you have to license someone's IP. The patent trolls are taking advantage of this. Look at how the company that was recently in the news that consists of several ex-Microsoft employees from their IP legal department are buying IP in order to sue. They are after the quick extortion buck in hopes of suing you into compliance so you pay them money for something they didn't even create and potentially is so obvious as to be incredibly offensive to most techs. The multiple desktop features in the OS is one example of the patent trolls trying to kill open source.

    Consider also that DOS was a derivative of the QDO

    --
    You can lead a man with reason but you can't make him think.
  41. Re:When did Linux stop being "cancer" & "commu by gujo-odori · · Score: 1

    That's because you didn't (so far as we know) spend a good portion of your life up until, say, 6 months ago, both doing everything you could to be incompatible with Christians and Christianity, and above and beyond that, threatening to persecute them, sometimes directly persecuting, and at other times getting others to persecute Christians on your behalf (think SCO).

    If you had done those things, it is likely that your Christian friends would view you with a great deal of suspicion (as St. Paul was initially viewed after his conversion), and it's even more likely that you would not even *have* any Christian friends, and you'd have to go out and try very hard to get some if you really wanted them. It's even possible that they might not believe you unless you actually became a Christian yourself and thereafter demonstrated a good track record as one. That's not saying you'd have to become an evangelist, but if you'd spent your life persecuting Christians and all of a sudden switched gears and tried to make nice, you'd have to understand if nobody trusted you unless you converted and established a five year track record as a solid Christian.

    When Microsoft has opened up its protocols and file formats, has released some significant software under the GPL or a BSD license, and has established a couple years of cooperating with open source, maybe throws in a bunch of patents, then people will start to believe that Microsoft is going to walk the walk. For now, they still look to most people like they're just talking the talk, and they'll have to be understanding if most people don't believe them, trust them, or want much to do with them. Especially since the situation on the ground is that FOSS can defeat Microsoft and the broader world of proprietary software *without* Microsoft's help, and it might even be counter-productive to cooperate with them. Put another way, Microsoft wouldn't be waving these olive branches around if they didn't think it was not only in their own self-interest, but more in their interest than FOSS's interest to try and play nice with FOSS.

    I used to work there until not all that long ago, and Microsoft employees are forbidden to even look at GPLed code, on the clock or off. The level of hostility to open-source in general and the GPL in particular is very high. Having been in that environment, I most especially don't believe Microsoft has turned over a new leaf, and so quickly. I'm certain they believe appearing to make nice with FOSS is better for them than it is for FOSS.

    If they release IE under the GPL or a BSD license sometime in the next two years, go ahead and call me wrong/paranoid/whatever you want. But I bet you won't get the chance :)

  42. The problem: they do not pay for their lessons by dscho · · Score: 2, Insightful

    It might well be that they learn (slowly, like the slowest of your "friends" in 1st grade), the lessons of open source.

    But then, they will not pay. They _claim_ to care about "intellectual property". But only when a _laywer_ that can _sue_ them, they will _respect_ the lessons to be something of value.

    So I will be glad when they are destroyed, once for all, and everybody else trying to _exploit_ others' work will have something to fear for.

    I mean, Microsoft _invented_ the notion that you should be paid for the _same_ work over and over and over and over again. Only they profited from that. And if you are not a Microsoft shill, you will _have_ to agree that this was unethical.

    Now they "learn" from Open Source? Well, even if they do, do they compensate those who taught them something?

    I guess not. So this planet will be better off if Microsoft dies a _violent_ death, discouraging all those parasites out there, trying to behave like Microsoft, too.

    1. Re:The problem: they do not pay for their lessons by Richard_at_work · · Score: 1

      I mean, Microsoft _invented_ the notion that you should be paid for the _same_ work over and over and over and over again. Only they profited from that. And if you are not a Microsoft shill, you will _have_ to agree that this was unethical._ Well, firstly copyright law is much older than Microsoft, so no - they did not invent that notion, and I don't even think they were the first software company to take advantage of it either.

      Secondly, I am not a Microsoft 'shill' (but you will find me defending them from time to time), and I don't see why such a thing just absolutely HAS to be classed as unethical.
  43. Re:When did Linux stop being "cancer" & "commu by FishWithAHammer · · Score: 1

    What is best is that the open source community continue it's uninfluenced progress toward the time when all software is developed in the same manner.

    You almost sounded reasonable until this line. Open-source software is not a fucking obligation. Who the hell are you to dictate what I can and can't do with something I create?

    --
    "You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
  44. Don't believe them. Learn = Stole by darkat · · Score: 1

    Open source believes in work, in fantasy, in the please one can get in doing something useful for the other people. A corporate environment is pervaded by power battles at every level of the organization and pressure from the market that often lead to sub-optimal choices and less that optimal products. Everything they can do is to stole ideas from OSS.

  45. It means they are going to copy Google by Colin+Smith · · Score: 1

    Hire tens of thousands of engineers throw some projects into the mix and see what comes out.

    --
    Deleted
  46. Re:RBN can learn from FOSS by Lorien_the_first_one · · Score: 1

    Don't forget the malware guys. The malware writers have been evolving quickly because they are sharing their tools and code. They are not exactly open source, but they are more open than Microsoft.

    In terms of time given to live, FOSS stands a much better chance of surviving attacks against malware than Windows due to MS's lack of comprehension of the benefits of truly open source development as well as security principles embraced by Unix from the beginning. They like BSD because they can steal from it. They don't like GPL because they can't take something and use it for themselves.

    Now, where am I going with this? Everything you have said is exactly the way I would like to say it, and there is no disagreement here. I just wanted to point out that when the I first learned about viruses, I learned that they were written by people who wanted to show the weaknesses in MS code. They did that.

    I look back and see that they were a subset of all malware writers. Once malware writers began to realize that it takes more than controlling PCs to impress potential girlfriends, they decided to start finding ways to make money at it.

    The ladder vs. the wall conflict in security will always favor open source due to the attributes you described: release early, release often, use open standards, use clearly described APIs, etc. MS hates to do this. In fact, they go out of their way to hide their APIs. Meanwhile, malware writers are throwing garbage characters at MS APIs to find a buffer overflow.

    So the only people outside of MS who take the time to figure out the weaknesses in the Windows product are criminals. The rest of the developer world will be focused on their own product or an open source product. Essentially, MS is on their own for security. And they're competing with open source development projects for mind share, to boot.

    Yeah, sure, people will pass bug reports to them once in awhile, but since their code is closed, so are their ears.

    Thanks for the great articles, Herm. You're quite vociferous and well stated at the same time.

    --
    The diversity and expression of human opinion is essential to human survival.
  47. Re:FOSS can learn from Microsoft by Anonymous Coward · · Score: 0

    A corporation will willingly sacrifice one of its own in order to make a profit. Or in Microsoft's case, sacrifice many from the community.
  48. Re:When did Linux stop being "cancer" & "commu by Allador · · Score: 1

    I'm confused.

    Why is this behavior 'stealing' and 'theft' when done by Microsoft, but nothing when done by an open source developer/project.

    I've got some reality-check news for you. Information wants to be free. This is a much more fundamental tenet than any FOSS stuff. So if you dont want people to duplicate your work, dont show it to them before you start selling it.

    But once its out there, and you show anybody, then unless NDAs were signed and enforceable, then anyone and everyone can take your ideas and make their own attempt at implementation.

    This is just reality.

    And this is beneficial to society as a whole. We wouldnt be anywhere if we didnt stand on the shoulders of everyone that has gone before us. And thats true of ideas, just as much as it is for source code.

    And whats this nonsense about pen computing being dead? Pen computing is huge in certain industries. The tablet features of Vista are terrific, and I'm not sure I've seen better on anything bigger than a handheld (though there may be other good implementations I'm not familiar with).

    In fact, things like Pen computing is a great example of where community drive open source fails. It's hard to get people interested in doing work like that, because a tablet user is often the most hard core cubicle-dwelling corporate road warrior. Or a doctor, or a manufacturing concern. There arent enough people willing to volunteer to do anything with it.

    So the only way you'll see good FOSS tablet functionality in a unix is if some corp does it and contributes it back for various reasons of its own.

  49. Re:When did Linux stop being "cancer" & "commu by Allador · · Score: 1

    When Microsoft has opened up its protocols and file formats, has released some significant software under the GPL or a BSD license, and has established a couple years of cooperating with open source, maybe throws in a bunch of patents, then people will start to believe that Microsoft is going to walk the walk. For now, they still look to most people like they're just talking the talk, and they'll have to be understanding if most people don't believe them, trust them, or want much to do with them. Especially since the situation on the ground is that FOSS can defeat Microsoft and the broader world of proprietary software *without* Microsoft's help, and it might even be counter-productive to cooperate with them. Put another way, Microsoft wouldn't be waving these olive branches around if they didn't think it was not only in their own self-interest, but more in their interest than FOSS's interest to try and play nice with FOSS. Who cares whether a very tiny percentage of the population thinks MS is 'walking the walk'? Your viewpoint as described here has very little relevance to what is going on.

    MS is a business, they're adapting their business to a changing marketplace where there is a lot more open source. They are doing what they need to do to survive and prosper. Thats their job.

    Only an idiot would suggest that Microsoft give up many billions of dollars per year of income in exchange for .... nothing except the goodwill of a tiny population that doesnt like it anyway. Why would anyone do that? You'd put huge amounts of people out of business and work.

    I used to work there until not all that long ago, and Microsoft employees are forbidden to even look at GPLed code, on the clock or off. The level of hostility to open-source in general and the GPL in particular is very high. Having been in that environment, I most especially don't believe Microsoft has turned over a new leaf, and so quickly. I'm certain they believe appearing to make nice with FOSS is better for them than it is for FOSS. Thats not hostility towards open source, thats pragmatic self-protection. They're doing everything they can to make sure that they have zero liability for copyright infringement on GPL code. That is the correct thing to do. Calling that hostile is just silly.
  50. No full access. by DrYak · · Score: 1
    I know you wanted to sound funny, but ...

    So, you're saying that all this time, open source proponents didn't know it was possible to use software they couldn't see the source to? Well, in that case...


    No sorry. If you don't have absolute full access to the software *and* code, if you are not in a system where the software you received *now belongs to you*, you'll never be allowed to do *whatever the fuck you want to do* with the software. For the free/libre software proponent, the access to source is a natural and obvious consequence that comes with the freedom granted to own and do whatever please with a software.

    A closed source software will always be limited to what the company decided to allow you to do.
    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:No full access. by bigstrat2003 · · Score: 1
      First of all: software I bought which is closed-source most certainly does belong to me, and I can do whatever the fuck I want with it. I do so all the time. Software is a limited thing, it can't do everything. Saying "you can't make your software do this"... well, maybe you should get other software that does? I mean, seriously, the whole "you can modify open-source" argument is rhetorical at best, because the vast majority of users can't. They simply don't have the knowledge. And if they tried to learn, they likely wouldn't have the talent for it (else we'd have a nation of programmers by now). In that case, how is open source any better?

      More to the point, modifying your software is not using it. Anyone can use their closed-source software to its fullest extent. The fact that they can't modify it is completely irrelevant to their ability to use it.

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    2. Re:No full access. by argiedot · · Score: 1

      It isn't that simple. I'm not a programmer, and when a game (Freespace 2 SCP) didn't work on my Via Unichrome graphics, I saw the error and just searched through the source for the size of textures to use and changed that down. There was tearing in the menus but the game itself was fine. That's what makes me so happy, the output from the program complained about some MAX_TEXTURE_WSIZE or something and I changed it. Maybe it isn't an acceptable trade for anyone, but it was for me. Perhaps we should just agree to disagree, maybe what I said doesn't apply to everyone, but it does to me, and my reason for getting people to try using free software is because I just want everyone to get a chance to be able to do what I managed there.

      Peace really.

  51. Re:When did Linux stop being "cancer" & "commu by gujo-odori · · Score: 1

    There are so many holes in that argument that it's not worth the time it would take to address them all. You're obviously a Microsoft fanboy and fail to realize that calling the GPL "a cancer" (Ballmer's exact words, in case your selective memory doesn't want to remember that), is not pragmatic self-protection. It's right up there on a par with his on-stage monkey dance antics when it comes to being professional and businesslike. When I say Microsoft is hostile to the GPL (and to open source in general, really), I truly mean hostile. The public evidence is quite clear on that, but for anyone who has worked there, it's a lot more clear.

    Your foot's stuck in your mouth and you don't even know it.