Comment: Re:American obesity (Score 5, Interesting) 172
Comment: Re:Dear MS trolls: (Score 1) 93
This difference is caused by the fact that hackers and malware programmers generally love GNU/Linux. Therefor they report the bug first, then disclose it to the public and never exploit it. For Windows bugs they do it exactly the other way around.
This is not the first time I've heard something like it, and I still don't understand it. How can all hackers and malware programmers "generally love" Linux so much that they don't attack Linux sites? Can this really be true? I don't see how, but for the sake of argument, assuming that statement is true, WHY would hackers and malware programmer loooovvvvvvvee Linux so much and not Microsoft that they protect Linux and attack Microsoft? Why?
Comment: An easy prediction: QT and Nokia part ways (Score 2) 329
-
From the Halloween documents (http://en.wikipedia.org/wiki/Halloween_Documents), specifically document 1 (http://www.catb.org/~esr/halloween/halloween1.html) and document 3 (http://www.catb.org/~esr/halloween/halloween3.html) ESR's analysis of how Microsoft perceives interacting with others:
To put it even more bluntly: "commodity" services and protocols are good things for customers; they promote competition and choice. Therefore, for Microsoft to win, the customer must lose.
Microsoft truly behaves as though it corporately believes that there's only a fixed pool of key ideas, most already discovered, which software designers must squabble over in zero-sum competition until the end of time. In that game, the only definition of `winning' is cornering enough goodies to guarantee you a monopoly lock.
- Micorosoft is a software company (even if it's run by a marketing execs); they make money selling software.
- Microsoft is an OS company; they make money selling an operating system.
- Microsoft is a for profit company that sells software for their operating system. They're not in the business of supporting other operating systems (example: the recent H264 plugin for Chrome is for Windows only Chrome. Some choice!)
- Microsoft encourages developers,developers,developers,developers, only so long as it improves their market share of operating systems. Any developer who competes with Microsoft software or whose product is deemed useful to Microsoft is either eliminated or assimilated (preferrably after running them into bankruptcy first -- see Spyglass and Internet Explorer -- http://en.wikipedia.org/wiki/History_of_Internet_Explorer)
- From wikipedia's entry on conflict resolution (http://en.wikipedia.org/wiki/Conflict_resolution) there are 5 strategies of resolving conflict: accommodation,avoidance,collaboration,compromise,and competition. Here's the definition of competition:
assert one's viewpoint at the potential expense of another. It can be useful when achieving one's objectives outweighs one's concern for the relationship.
Here's the definition of accommodation:
surrender one's own needs and wishes to accommodate the other party.
- In any negotiations with Microsoft one might assume that because Microsoft is a corporation composed of many individuals that negotiations will involved either collaboration or compromise. However, you need to keep in mind that Microsoft believes in zero sum --- in order for them to win, you have to lose. Which means that in the process of negotiations with Microsoft you'll be going through the following stages of negotiation:
- Assume collaboration. You'll explain your requirements and assume they will explain theirs and you'll assume you'll find a way to satisfy both. However, this won't happen as Microsoft want to win by making you lose, so they won't accede to your suggestions.
- Since you don't get everything you want you'll assume the strategy has switched to compromise, clearly you're giving some to Microsoft, and you expect them to give some concessions in return to you as a way of compromising. But, Microsoft believes in zero sum, and its strategy is competitive. Microsoft gives no concessions, only face saving rationalizations so you can convince yourself that you're getting something from them.
- Whether you realize it or not, your strategy has now become accommodation. To save face, you delude yourself into believing you're an equal partner with Microsoft until it's too late.
Let's analyze the Nokia-Microsoft "deal". What has Microsoft gained?
- Nokia is using Microsoft's operating system. (No Linux need apply. Die symbian, die!)
- Nokia is using Microsoft's api instead of another. (No qt is allowed)
- Microsoft is getting a large slice of the cell phone market exclusively. (Don't have to compete with Android for Nokia)
- Microsoft has exclusive control of the software. (Talk about a wet dream for Microsoft!)
What has Nokia "gained"?
- Loss of their own operating systems.
- Loss of the direction of the software for their cellphones. (That's Microsoft's purview now.)
- Loss of their Symbian, Qt, and Meego developers (what do they need them for now? They're nonprofitable baggage now.)
In summary it looks to me like the bargaining resolution was a (competition, accommodation) pairing with Microsoft in the drivers' seat. If I was on Nokia's board or a shareholder I would probably demand an investigation into fraud and at the very least fire Elop.
- In any negotiations with Microsoft one might assume that because Microsoft is a corporation composed of many individuals that negotiations will involved either collaboration or compromise. However, you need to keep in mind that Microsoft believes in zero sum --- in order for them to win, you have to lose. Which means that in the process of negotiations with Microsoft you'll be going through the following stages of negotiation:
Comment: Does't know Kerkchoff's Principle (Score 1) 258
Comment: Re:well written apology for Mr. Gates' behavior (Score 2, Interesting) 286
Justice Department Seeks Ebonics Experts 487
from the my-mama-no-raise-no-dummies-I-dug-her-rap dept.
Comment: The public first (Score 1) 126
Let me just start with a wikipedia entry, on Kerchoff's principle: http://en.wikipedia.org/wiki/Kerckhoffs'_principle
If you get the point of Kerchoff's principle, you understand why *if* all things are equal *then* open source code is inherently better than closed source code because public disclosure finds the flaws in the source code faster so they can be fixed faster.
If you want to force a *proprietary* vendor to *immediately* fix a vulnerability, you have to disclose it to the public first, as the vendor will have to scramble to fix the vulnerability or risk losing angry customers.
Talking to the vendor first results at best in delay and/or inaction by the vendor, and at worst threats of lawsuits and criminal prosecution by the vendor should you disclose the vulnerability to the public.
It's like that video by that law professor, the one that advises you not to talk to police. Here's the url: http://video.google.com/videoplay?docid=-4097602514885833865#
In the case of an open source vendor, the code is open to anyone to inspect, and hence is easier to fix. This is why for example Mozilla and Google offers bounties to anyone for finding bugs. They are *actively* encouraging people to find flaws so they can be patched. This is why open source code is better.
Comment: Re:Telling people to use windos when you use Linux (Score 1) 718
Comment: There's at least *1* fatal flaw with this concept (Score 1) 293
One key point about the Linux package managers is that they are needed to manage *all* that open source software. Why open source software? Because no (or rather very few) proprietary companies provide proprietary software for Linux. So if you want some kind of functionality under Linux your best option is to write an open source version because there is very little proprietary software for Linux.
Why then is package management bad for Windows, if it's so useful for Linux? Well, because package management is effective if you have can pull source code, compile, and determine dependencies. That means an open source license for the source code. That means that Microsoft is telling it's huge "ecosphere" of proprietary software vendors to "Piss off you sod!", because *their* software doesn't fit the package management model. That leaves 2 possibilities in the Microsoft world:
- The package manager is successful and really takes off. Which means most software is open sourced and provided packaged by Microsoft and the proprietary vendors are so screwed out of existence, as they are no longer needed if you can just do an "apt-get install" on Windows without the vendors.
- The independent vendors realize the implication of this package manager and what it means to their bottom lines and either threaten to leave the Microsoft world for Apple OS X or Microsoft drops the package manager idea.