Making Open Source Pay 31
cenonce writes "This short, but informative, article over at Tom's Hardware Guide does a nice job of explaining the difference between Closed and Open Source Software and how it can save the suits money (as well as make the tech staff's lives easier)."
FP (Score:2, Redundant)
Re:FP (Score:1, Offtopic)
Freedom, not gratis.
Re: "Free as in speech, not free as in beer." (Score:5, Insightful)
A better simile, I've found, is to compare their computers to a delivery fleet. It's fairly obvious to even a PHB that a fleet of vehicles needs maintenance. And, while they might not want to get their hands dirty working on the innards of their vehicles, they know enough to hire mechanics for that. And those mechanics need the shop manuals for all the vehicles.
Tell them that "closed source" software is a lot like a vehicle without a shop manual. If something goes wrong with such a vehicle, all you can do is report it back to the auto company that you bought the vehicle from. They'll fix it when they get around to it. Or maybe they won't bother fixing it, figuring that they can get you to buy a new vehicle if they drag it out long enough or say it's not repairable.
Similarly, you tell them, things are going to go wrong inside their computers. You need "shop manuals" for all your software. With software, that's called "source code". If your computer support group doesn't have the source code, then they'll be stuck with just reporting problems back to the software vendor. And that vendor will be just about as interested in fixing your problems as the truck manufacturerer is interested in keeping your fleet running. More likely they'll try to sell you more (New! Improved!) software.
But if your people have the source code (for software) or shop manuals (for vehicles), they can dig in, figure out what's wrong, and fix it.
Yeah, studying the source isn't easy. But have you ever leafed through a shop manual? There are people who can understand those things. And, as with mechanics, the software people have friends and colleagues that share information about problems. With software, this is mostly done via the Internet, and you really want your IT people to know how to use it to find information.
Most managerial types are smart enough to understand all this. We just have to get across to them that trusting software vendors is no smarter than trusting auto dealers. You need your own people to do the job, your people need the information required to do the job, and they also need to communicate with their cohorts in other organizations to find information fast when something's failing. But without the source code, there's often nothing your people can do, and you're stuck with begging the dealer for help.
Re: "Free as in speech, not free as in beer." (Score:5, Funny)
Quite possibly the best quote I've ever read on
Re: "Free as in speech, not free as in beer." (Score:3, Insightful)
Heh; I'll be happy to take credit for it. Actually, I've seen very similar comments from other people. But feel free to spread the meme:
Trusting software vendors is no smarter than trusting auto dealers.
And you can easily follow this with the explanation that open-source software means that you don't have to trust the software vendor. You can (hire people to) take a look at the source, fix bugs, and add features. And, most importantly, you (or yo
Re: "Free as in speech, not free as in beer." (Score:2)
Not auto dealers, auto *makers*. There's (IMHO, anyway) a substantial difference.
Make Open Source Pay (Score:1, Offtopic)
What a lame article.... (Score:2, Insightful)
Come on mom, I don't know why Mozilla is crashing, just download the source from CVS and fix it yourself.
Just shows how out of touch the open source community is.
Along with your lame HOWTO's that are based on builds 3 verions back.
Re:What a lame article.... (Score:2)
Re:What a lame article.... (Score:1)
A little too biased. (Score:2)
Re:A little too biased. (Score:2)
However just yesterday I gave up on a searching in MSDN after most of the day and started doing Google to locate an explanation for a Windows problem. Google revealed in 1/2 hour that I could not write what I wanted (even this information was difficult to locate, but at least somebody finally complained and others in mailing lists confirmed this).
[the problem I was having was trying to figure out if I could get it so that _fopen() took a string in UTF-8. This is reall
The problem with Open Source (Score:3, Interesting)
I love the idea of open source, I just can't see any way to make a living doing it.
Re:The problem with Open Source (Score:2)
Re:The problem with Open Source (Score:2)
Nice job if you can get it though- too bad there's such a vanishingly small number of such jobs that we st
Re:The problem with Open Source (Score:2)
Which works fine if you're a good salesman OR have a nice understanding bank which doesn't mind a missed house payment or two.
Re:The problem with Open Source (Score:2, Interesting)
Re:The problem with Open Source (Score:2)
Re:The problem with Open Source (Score:2)
Let's say you provide people with source code, under one of the mainstream open source licenses. You can charge for open source, everyone says so. So you charge, say, fifty bucks for a well done product. So far so good, right?
Six months later, some creep decides you're charging too much, takes moral offense at your "greed" and starts a BitTorrent of your whole software distribution, available for free. Bling. Out of business. So much for that. And almost every
Re:The problem with Open Source (Score:2)
Mod parent up +1 Insightful (Score:2)
it's not "as in beer" but "as in speech" for me. (Score:2)
In short, they love free stuff but think anything their company has put any resources into (i.e. paying me to code bits into) belongs to them even if it's GPL'd. Perhaps not major GPL violations but stuff that really should be released. This is the boss-education issue for me.
That said they're not all