Slashdot Mirror
Interclue and What Going Proprietary Can Do
Linux.com (which shares a corporate overlord with Slashdot) has an interesting look at what going proprietary can mean for your overall effectiveness. Using Firefox extension "Interclue" as the object lesson, the piece looks at both the engineering and social difficulties surrounding the project. "Even more significantly, the efforts to commercialize only detract from the software itself. The basic idea behind Interclue would make for a handy Web utility, but seems too slight to build a business around. The effort to do so only leads to complications that do nothing to enhance the basic utility, and to pleas for donations that can only annoy. The result is that, if your position on free software doesn't lead you to avoid Interclue, the efforts to monetize it almost certainly will."
Your Newspeak is ungood. "bad" is ungroupthink. Use "doubleplusungood".
Fascism starts when the efficiency of the government becomes more important than the rights of the people.
After all, OS_X is the merging of proprietary and open source as well.
I think this current example presented the way it has is a bit propagandistic.
Both OSS and Proprietary have their virtues and vices, and it's a question of the project manager's competence whether or not a project brings out more of the former or the latter.
VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
What's with the incoherent summary? Nowhere in the summary did this even mention what "Interclue" was supposed to do, and why we should care about attempts to "monetize" it (lame corporate speak when applied outside the finance world).
Editors must be sleepwalking through the end of '08.
(-1, Raw and Uncut is the only way to read)
Software history tends to repeat itself. I remember back in the 1980s, when software distributed on floppy disks often had copy protection. Legitimate users voted with their feet, because it was too much of a nuisance -- e.g., you couldn't back up your software. Software houses eventually got the message and stopped doing it. Now, a generation later, we seem to be going through the same silliness again, except that now they call it DRM.
Similar deal with these little proprietary pieces of crapware. Back in the 90s, there was a period when the internet had gained quite a bit of mindshare, but OSS hadn't. During that time, you'd get people posting lots of trivial little pieces of software on the web, with various schemes intended to extract some small amount of money from the customer: nagware, adware, shareware, crippleware, ... That whole scene was a total dead end. In most cases, programmers found that the amount of revenue they got was essentially zero; this was the users indicating that although the software was somewhat useful to them, it wasn't useful enough to pay money for. Then OSS started getting popular, and most clueful users started to realize that it was a better way to go. Now we have some new software platforms -- firefox+xul, browser+ajax, and the iPhone -- and everyone seems to need to learn the same lesson all over again. At some point, the users who didn't go through this in the 90s are going to realize some of the same things. They're going to realize that spending $5 or $10 on lots of little pieces of software will eventually add up to real money. They're going to realize that it's a hassle to have to keep track of all the software, registration numbers, etc. They're going to realize that it's no fun to have to go back and reproduce this whole set of proprietary apps every time they buy new hardware.
Find free books.
The basic idea behind Interclue would make for a handy Web utility, but seems too slight to build a business around.
To rephrase: If your product isn't valuable enough for people to spend money on, it will be hard to make money selling it. The rest of the article is a fairly well-written review of an obscure add-on, with very little insight about open vs. proprietary software.
/...