Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Daveydweeb explains that Vankin bases his argument on factual errors, poor reporting and a shoddy understanding of the website itself. The whole debate raises an important question, though: is Wikipedia just too insular for the layperson to understand?"It is a question of time before the Wikipedia self-destructs and implodes. [...] People who are regularly excluded or at least moderated in every other Internet community are welcomed, no questions asked, by this wannabe self-styled 'encyclopedia'
4. The Hater
I detest you Fanboy. Everyone knows that Mactendo release only the poorest of products, that its designers are nothing more than a team of monkeys and that its CEO is, in fact, a baboon. Despite never actually having been in the same room as a Mactendo product, I have nothing but the greatest contempt for anyone who espouses allegiance to Mactendo. I will now impugn Mactendo by making a snide reference to a feature which Microsony products have always enjoyed, but which Mactendo products lacked in the mid 1980s. I will not rest until all Mactendo supporters renounce their faith and embrace their Microsony overlords.
8. The 1337
As part of the online elite who have long ago done away with the need for vowels, I am crafting my post exclusively from esoteric strings of cryptic, and arbitrarily capitalised, alpha-numeric sequences. Everyone who reads this will thereby immediately understand that I can best them at every computer game ever invented. I would say more, but my thumbs hurt."
Since I am going to sell it, I've been struggling with the question of just how much my little program is worth. And the question really goes beyond my little program to the value of so-called "Intellectual Property" in general.
My program solves a particular niche problem in the electronics industry, and would be useful to certain hobbyists as well. A business would easily save hours of engineering time using this software for a single project, so I don't think it's at all unreasonable to charge hundreds of dollars for it.
On the other hand, a hobbyist may find the time spent doing it the hard way to be enjoyable in it's own right, and find the program almost valueless on that basis. Or maybe they just want to toy with it, but wouldn't be willing to cough up $50 to do so. But maybe they would for $5.
If my price is to high, I lose a sale. Whether I lose that sale to "piracy", or to someone just doing without a useful tool is irrelevant. If my price is too low, I'm not reasonably compensated for my work.
It comes down to the fact that the value of any sort of "IP" is just what the buyer thinks it is worth to him. My question is, how can I arrive at a fair price for each sale?
- I could have different prices for commercial versus personal use, but that isn't really fine-grained enough.
- I could charge royalties, but we all know how popular royalty based compiler licenses are.
- I could move critical functions to a server and make it pay-per-use, but what is a "use" worth?
- I could offer it as shareware, but that really doesn't solve the problem. I can't bring myself to pay $90 the author is asking for a piece of software I occasionally use, but I would have registered it long ago for $20.
- I could ask people to name their own price, but then Global Mega Electro Corp would offer me $0.50 for a site license.
- I could negotiate each purchase individually, but I get irked when companies want my name and address. I'd never put up with "So, what exactly do you intend to write with this copy of Word?"
So, Slashdotters, how should I arrive at the correct number?"
Now Microsoft has launched a repackaging of the Sysinternals tools in a single suite as well as providing all of the tools the gained with the purchase as singles utilities. The down side to all of this is that Microsoft have decided not to release any source code, so it appears some of those un-trusting people were right all along. Anyway at least the tools are still available even if the underlying source code is now closed.
For more on this see the M$ web site for the sysinternals tools in MS Technet — Sysinternals"