Slashdot Mirror
Cash Value 1/10 of a Cent
goombah99 writes "It happens all-too-often that the govenment and companies negligently reveal citizen's private information on their websites. When collection of this information is something required by law there is an obligation to protect it. But is privacy a 'property' and does its loss require compensation? Wired news reports 'The Supreme Court will hear oral arguments Wednesday over whether the federal government should reimburse individuals whose sensitive data was disclosed illegally, even if no harm can be proven. At issue before the court, according to privacy advocates, is how valuable privacy really is.'"
and I wasn't even trying! Woohoo!
...your civil rights depend on for which company you work and what civil rights that company has lobbied.
The High Priests of the Bazaar
This paper presents a case against the open source movement and explains why the open source model does not work economically for the vast majority of those involved in the production of commercial software. There are several arguments against the OS (open source) model.
Open Source Doesn't Make Economic Sense For Most
The open source organization has presented a few cases that supposedly explain why OS works economically. However, if you examine the cases objectively you will find that the cases are flimsy and non-specific and do not address any specific concerns. They attempt to bolster their case by pointing out a few "successes", among which Caldera (now called SCO) and Red Hat are displayed as shining examples.
The real economic question of the OS model is how is money made, and who is making the money. Who is being rewarded financially for the enormous development effort? The open source initiative claims that there are at least four different models that allow someone to reap rewards. Oddly, it is not mentioned that it is not necessarily the people who did the development work that gain financially.
The four primary business cases mentioned by OS proponents are "Selling Support", "Loss Leader", "Widget Frosting" and "Accessorizing."
The first case proposes that money can be made via selling support for the free software product. This is by far the strongest case and is proven to work, for a few small companies. The two companies that are shown as positive examples of this business model are Red Hat and Caldera, who distribute and support the Linux operating system. What is never mentioned is that neither of these two companies has contributed significantly in relative terms to the Linux development process. Its important to note that using this business model, the people that make the money are usually not the ones who have invested in the development process. So much for the strongest case.
The second case is based on the idea that you give away a product as open source so you can make money selling a closed source program. This also can work, but it should be noted that the money is being made off the closed source product and not off of the open source. An example of this model would be Netscape, who gives away the source code of their client browser so the OS community can do development, but keeps their "cash cow" products completely closed. Obviously, this case may only work if you have a software product that lends itself to this sort of "give away the razor and make money on the blades" system. The truth is that the vast majority of software is monolithic. So much for the loss leader case.
The third case, "Widget Frosting", sounds completely practical. The premise that hardware makers produce open source software so that the OS development community will work for free to produce better drivers and interface tools for their hardware products. It sounds great on the surface, especially for the company that produces the hardware: they get free drivers and do not have to pay for expensive developers. The OS community wins by getting presumably stable drivers and tools. What is not mentioned is the reason hardware makers usually don't do this is because they do not want to reveal trade secrets regarding their hardware design. Production of efficient drivers requires an intimate knowledge of the hardware the driver is for. It is almost always the case that it is in the hardware developers' best interest to keep their hardware secrets close to home. This also brings up the question of why isn't hardware "open"? So much for the frosting case.
The final case, "Accessorizing", is similar to the first, but throws in the idea of selling books and complete systems with the open source software, and other accessories as well. It is obvious that selling books qualifies as support, and that it really belongs in the first case. The idea of selling computer systems, T-Shirts, dolls, again begs the question: "Who is making
There are two aspects to the question of how it feels to get your dick sucked:
1) The physical sensation.
2) The interpretation of the physical sensation, which combined with other things, ends up being your actual experience.
(1) above is certainly the same in both cases -- modulo poorer or better technique, and so on and so forth -- but (2) is certainly different depending on your 'state', which is of course dependent, in part, on the way you frame the event. The different way that you frame the events of getting sucked off by Heidi Klum or the fat chick next door will cause you to experience the events differently, even if the 'objective' physical sensations were exactly the same. Since there is no unmediated access to the world -- ask any cognitive scientist -- the fact that the physical sensation (as in nerves stimulated in your cock) is the same is irrelevant, because that is just one relatively small input into the recipe for orgasmic bliss that is the good bj.
Hope this helps. I'll be here all week.....