Two innovative revenue models for a free piece of software(blog.digsby.com)
blog.digsby.com
Two innovative revenue models for a free piece of software
http://blog.digsby.com/archives/693
7 comments
Just some quick responses:
"Compare our industry to Medicine and Law. It's actually illegal for people who aren't doctors or lawyer to dispense medical advice or legal advice."
Dispensing bad medical advice can result in serious injury or death. Dispensing bad legal advice can result in long prison sentences. Writing bad software wastes time and costs money. Industries where software CAN kill people are more stringent with their development and hiring practices because of their liabilities.
"Oh, I know lots will cringe at the thought of that. I know the thought is that stuff like this subsidizes crappy coders through artificial scarcity."
We all know that good programmers are scarce. The reason we cringe is because no one knows of a good method to draw the line between good programmer, and not-good-enough programmer, in a world where programmers do so many different domain-specific things.
"I see so many people without a background in programming write poorly architected code that performs like a dog and just breaks... it breaks because some wanabe hacker just jumped in and started hacking without knowing wtf (s)he was doing and it ends up costing the company paying for the work more money later on."
This is how people get their background in programming, by writing poorly architected code, watching it perform like a dog and break, and then fixing those issues. That is what gaining experience looks like. Companies that hire inexperienced junior level programmers and trust them with large architectural decisions have made a managerial mistake, do not blame the novice programmer for this.
--- And on open source ---
Much of open source revolves around building and maintaining tools that support people in our trade. Having open libraries, operating systems, servers, text editors, compilers, etc, helps everyone out there be more a more productive software developer. Other professionals also look out for each other and work collectively to advance their profession generally. We are no different, it just happens that due to the nature of our field, we have much more powerful mechanisms to do so at our disposal.
"Compare our industry to Medicine and Law. It's actually illegal for people who aren't doctors or lawyer to dispense medical advice or legal advice."
Dispensing bad medical advice can result in serious injury or death. Dispensing bad legal advice can result in long prison sentences. Writing bad software wastes time and costs money. Industries where software CAN kill people are more stringent with their development and hiring practices because of their liabilities.
"Oh, I know lots will cringe at the thought of that. I know the thought is that stuff like this subsidizes crappy coders through artificial scarcity."
We all know that good programmers are scarce. The reason we cringe is because no one knows of a good method to draw the line between good programmer, and not-good-enough programmer, in a world where programmers do so many different domain-specific things.
"I see so many people without a background in programming write poorly architected code that performs like a dog and just breaks... it breaks because some wanabe hacker just jumped in and started hacking without knowing wtf (s)he was doing and it ends up costing the company paying for the work more money later on."
This is how people get their background in programming, by writing poorly architected code, watching it perform like a dog and break, and then fixing those issues. That is what gaining experience looks like. Companies that hire inexperienced junior level programmers and trust them with large architectural decisions have made a managerial mistake, do not blame the novice programmer for this.
--- And on open source ---
Much of open source revolves around building and maintaining tools that support people in our trade. Having open libraries, operating systems, servers, text editors, compilers, etc, helps everyone out there be more a more productive software developer. Other professionals also look out for each other and work collectively to advance their profession generally. We are no different, it just happens that due to the nature of our field, we have much more powerful mechanisms to do so at our disposal.
> As I flipped through, I realized, this isn't a book of home plans, it's a catalog for plans that you can buy.
Actually, it's a book of dreams. Most folks who buy that book will never build a house, but they'll look at that book and dream about doing so.
Many books/publications are much the same.
Actually, it's a book of dreams. Most folks who buy that book will never build a house, but they'll look at that book and dream about doing so.
Many books/publications are much the same.
Here's an example of an "industry" that gives away the product of their work for free: academic research.
Now in this "industry" the free flow of this product has allowed people to build on the shoulders of giants and arguably made a big contribution to the world.
Likewise I notice that these days when we are building, for example, various embedded gizmos, we can suddenly achieve a far higher level of functionality, integration, communication etc -- because we no longer have to write (or buy in) building blocks such as TCP/IP stack, memory management or whatever.
So open source greatly facilitates this "standing on the shoulders of giants"...
Now in this "industry" the free flow of this product has allowed people to build on the shoulders of giants and arguably made a big contribution to the world.
Likewise I notice that these days when we are building, for example, various embedded gizmos, we can suddenly achieve a far higher level of functionality, integration, communication etc -- because we no longer have to write (or buy in) building blocks such as TCP/IP stack, memory management or whatever.
So open source greatly facilitates this "standing on the shoulders of giants"...
You severely misunderstand academic research. It is "given away" to get more research funds, to advance one's career inside academia, and to abide by the guidelines of the previous money you have taken.
EDIT: For some it's "given away" to fill some deep hole in one's ego.
EDIT: For some it's "given away" to fill some deep hole in one's ego.
I used to be an academic, with industrial research projects, for some time, so I'm relatively confident I understand how academia works.
1. I wasn't suggesting at all that academic research isn't paid for. Clearly the people doing the work somehow earn money and make a living, some of them exceedingly well. Nowhere was I suggesting that people do academic research for the pure love and charity of giving stuff away for free.
2. In large part, everyone gets to share and benefit from their output -- and most of those benefiting would have had no direct financial involvement with the work.
So, here we have a model where the product is available for free while the creators somehow earn a living (probably by being domain experts or by knowing how to apply their free "product" in the context of something more specifically revenue generating).
How is there not a correlation with; and a counterexample to; some of the arguments from the parent comment?
1. I wasn't suggesting at all that academic research isn't paid for. Clearly the people doing the work somehow earn money and make a living, some of them exceedingly well. Nowhere was I suggesting that people do academic research for the pure love and charity of giving stuff away for free.
2. In large part, everyone gets to share and benefit from their output -- and most of those benefiting would have had no direct financial involvement with the work.
So, here we have a model where the product is available for free while the creators somehow earn a living (probably by being domain experts or by knowing how to apply their free "product" in the context of something more specifically revenue generating).
How is there not a correlation with; and a counterexample to; some of the arguments from the parent comment?
So, here we have a model where the product is available for free while the creators somehow earn a living (probably by being domain experts or by knowing how to apply their "product" in the context of something more specifically revenue generating).
Journals are not free at all. While many get access to literature through JSTOR, or some similar service, just for being affiliated with a research institution in one form or another, it's not cheap for those outside of the system or for those providing you access to JSTOR. My point is that the "industry" of academic research is not giving anything away for free. It's a business just like any other business.
Journals are not free at all. While many get access to literature through JSTOR, or some similar service, just for being affiliated with a research institution in one form or another, it's not cheap for those outside of the system or for those providing you access to JSTOR. My point is that the "industry" of academic research is not giving anything away for free. It's a business just like any other business.
This just sounds like nitpicking, its like saying that open source authors are not really giving anything away for free because the person downloading the code is getting charged by his ISP for the broadband access.
Sure there is a business of distribution, of getting the product to you, but this has nothing to do with either the creation or the inherent value of the product itself.
For example, lets say you pay $10 or whatever to purchase via IEEE a pdf of a paper that details a new way of solving a specific problem with patch antennas. How does the value of those findings correlate with that $10?
Sure there is a business of distribution, of getting the product to you, but this has nothing to do with either the creation or the inherent value of the product itself.
For example, lets say you pay $10 or whatever to purchase via IEEE a pdf of a paper that details a new way of solving a specific problem with patch antennas. How does the value of those findings correlate with that $10?
When you did industrial research, how many things involved just one paper? I'm not trying to create an argument. I just accept that academic research is not as pure as many people portray it to be. I used to think the university/research system was a pristine place of people doing research for the sake of research. I don't think that anymore.
I'm not by any stretch saying that academic research is pure, at all. But I don't see how that is relevant.
It feels akin to my surprise in other threads where some people insist e.g. that there is inherently something "bad" when a company like MS releases source to the linux community, because they didn't do it purely for giving things away and there must be some ulterior motive.
Why does it matter? I guess it matters to people if they perceive the world as a 0-sum game, so there is always a "take" side to the "give".
But I don't see it proven that the world indeed functions as a 0-sum game. We are all scratching our own itches, we perhaps all have ulterior motives in "giving things away" and yet we can earn a living while the world at large benefits from the fact that we did give things away.
For example:
Some time ago I had to add code to the linux kernel because of problems in autodetecting the volume resolution of a particular audio codec IC. Either no one had discovered it before or it was not a priority for other people, since there was no fix for it at the time. But it was a problem for my client, so they paid to fix it. There was no hesitancy in open sourcing the patch, since it is a building block and them giving it up has 0 implication on their business.
Also they had an ulterior motive in doing so, because having the fix in mainline meant they would not have to keep merging it in while staying up to date with kernels, and would not have to worry if certain code structures change at some future point, etc.
Since they had run into the problem it is likely that someone else would also have run into it at some point; and by that patch being available, someone else is going to be saved some time and expense (except for the $0.00012 or whatever "distribution" fee to download the code), and maybe that person gets to spend an extra hour with his kid.
Who loses in this case?
Or more recently where a client had a problem with an SoC where there is a timing problem in the macrocell relating to the interrupt controller, and boards based on that SoC would mysteriously stop working under some conditions. Again this was a problem, they paid to get a software fix for it, and the fix will be submitted to the community. Again there is an ulterior motive, because more people will get to test & debug the fix on a wider variety of environments which will save the client time in the long run; and again this is going to save headaches, hassles, money and possibly lawsuits for other parties.
So in both cases an "impure" "giving away for free but with ulterior motives" and everyone stands to gain?
Obviously academia is of a different scale, but it seems to me more of the same thing -- hey we need to publish in order to improve our career prospects, but how does anyone loose from this?
And to answer your question: it varied. On one short project I purchased six papers (iirc); on one multi-year project I purchased one. In the latter case much of the research had already been embodied into available standards, and often times it was possible to pop an email right to the author.
Many years ago I was doing research in TCP over satellite connections in Africa; shot an email to Mark Allman in the USA, and received their full experimental TCP Vegas implementation by return email. Who looses here?
I just don't know how else to phrase this; we all keep going on with our work but there are many things we can actually share (that may directly benefit us and appear as ulterior motives); that ends up making life easier.
Surely this is way more efficient than the alternative (not sharing), even if you have the "middleman/distribution channel" taking a nickle?
It feels akin to my surprise in other threads where some people insist e.g. that there is inherently something "bad" when a company like MS releases source to the linux community, because they didn't do it purely for giving things away and there must be some ulterior motive.
Why does it matter? I guess it matters to people if they perceive the world as a 0-sum game, so there is always a "take" side to the "give".
But I don't see it proven that the world indeed functions as a 0-sum game. We are all scratching our own itches, we perhaps all have ulterior motives in "giving things away" and yet we can earn a living while the world at large benefits from the fact that we did give things away.
For example:
Some time ago I had to add code to the linux kernel because of problems in autodetecting the volume resolution of a particular audio codec IC. Either no one had discovered it before or it was not a priority for other people, since there was no fix for it at the time. But it was a problem for my client, so they paid to fix it. There was no hesitancy in open sourcing the patch, since it is a building block and them giving it up has 0 implication on their business.
Also they had an ulterior motive in doing so, because having the fix in mainline meant they would not have to keep merging it in while staying up to date with kernels, and would not have to worry if certain code structures change at some future point, etc.
Since they had run into the problem it is likely that someone else would also have run into it at some point; and by that patch being available, someone else is going to be saved some time and expense (except for the $0.00012 or whatever "distribution" fee to download the code), and maybe that person gets to spend an extra hour with his kid.
Who loses in this case?
Or more recently where a client had a problem with an SoC where there is a timing problem in the macrocell relating to the interrupt controller, and boards based on that SoC would mysteriously stop working under some conditions. Again this was a problem, they paid to get a software fix for it, and the fix will be submitted to the community. Again there is an ulterior motive, because more people will get to test & debug the fix on a wider variety of environments which will save the client time in the long run; and again this is going to save headaches, hassles, money and possibly lawsuits for other parties.
So in both cases an "impure" "giving away for free but with ulterior motives" and everyone stands to gain?
Obviously academia is of a different scale, but it seems to me more of the same thing -- hey we need to publish in order to improve our career prospects, but how does anyone loose from this?
And to answer your question: it varied. On one short project I purchased six papers (iirc); on one multi-year project I purchased one. In the latter case much of the research had already been embodied into available standards, and often times it was possible to pop an email right to the author.
Many years ago I was doing research in TCP over satellite connections in Africa; shot an email to Mark Allman in the USA, and received their full experimental TCP Vegas implementation by return email. Who looses here?
I just don't know how else to phrase this; we all keep going on with our work but there are many things we can actually share (that may directly benefit us and appear as ulterior motives); that ends up making life easier.
Surely this is way more efficient than the alternative (not sharing), even if you have the "middleman/distribution channel" taking a nickle?
Actually,
I used to be involved medical software. And, yes, you do go to federal pound me in the a$$ prison if MEDICAL software you create has bugs in it. The whole FDA approval thing cuts two ways, and it is a VERY sharp blade. That's why most software engineers won't write such software. How long could they stay out of prison using PHP or Python? Imagine a trauma center's server going down. Yep! Off you go to prison son. A missed tumor because your imaging code did not bring out enough contrast. That's good for 7 - 12 years. The lack of guarantees in the floating point code alone is probably enough to get a lot of these guys 5 to 10.
And yes, it has happened . . . several times!
These sorts of laws would make you code like your life depends on it . . . because it does.
Be careful what you wish for. That's all I can say.
I used to be involved medical software. And, yes, you do go to federal pound me in the a$$ prison if MEDICAL software you create has bugs in it. The whole FDA approval thing cuts two ways, and it is a VERY sharp blade. That's why most software engineers won't write such software. How long could they stay out of prison using PHP or Python? Imagine a trauma center's server going down. Yep! Off you go to prison son. A missed tumor because your imaging code did not bring out enough contrast. That's good for 7 - 12 years. The lack of guarantees in the floating point code alone is probably enough to get a lot of these guys 5 to 10.
And yes, it has happened . . . several times!
These sorts of laws would make you code like your life depends on it . . . because it does.
Be careful what you wish for. That's all I can say.
wow, that's crazy. If a doctor makes a mistake like that they don't go to jail! how does that work?? it doesn't even make sense!
As I wrote above:
Punishments are generally so harsh because it is considered fraud. The defendants were selling software that didn't work. They either knew it did not work, in which case it is pretty much straightforward fraud, and God help them if someone dies. Alternatively, they did not know that the software did not work. In which case they committed fraud when they represented themselves to the health care organization that purchased the device as being qualified to make a determination as to the efficacy of the software or device. Again, God help them if someone dies.
But all of that is really beside the point.
The fact is that in order to get your software FDA approved you signed off on literally thousands of legally binding sheets of paper. The short version of these sheets of paper is that you guarantee, for instance, that the software ran an 8bit lut through a 10bit colorspace so that the full range of that 10bit colorspace would be visible in the 8bit window at one time or another. That is actually a fairly standard guarantee that medical software makers have to give. If your software does not give the appropriate contrast at a given setting, then the FDA knows that you and whoever else signed that sheet of paper lied. You could not have tested it for all values. This is fraud.
Or let's say your software flips images left for right. You guessed it, there is a slip of paper you and a lot of other people sign indicating that your software will not do that. You also gave that slip of paper to the FDA to get FDA approval. Later some poor nurse somewhere is prepping the left leg for amputation instead of the right one. The doctor cross checks with the FDA approved software, and verifies that the problem is in the left leg. And . . . do you see where this is going? This too is fraud. And it is criminal in the United States. You WILL be prosecuted.
Punishments are generally so harsh because it is considered fraud. The defendants were selling software that didn't work. They either knew it did not work, in which case it is pretty much straightforward fraud, and God help them if someone dies. Alternatively, they did not know that the software did not work. In which case they committed fraud when they represented themselves to the health care organization that purchased the device as being qualified to make a determination as to the efficacy of the software or device. Again, God help them if someone dies.
But all of that is really beside the point.
The fact is that in order to get your software FDA approved you signed off on literally thousands of legally binding sheets of paper. The short version of these sheets of paper is that you guarantee, for instance, that the software ran an 8bit lut through a 10bit colorspace so that the full range of that 10bit colorspace would be visible in the 8bit window at one time or another. That is actually a fairly standard guarantee that medical software makers have to give. If your software does not give the appropriate contrast at a given setting, then the FDA knows that you and whoever else signed that sheet of paper lied. You could not have tested it for all values. This is fraud.
Or let's say your software flips images left for right. You guessed it, there is a slip of paper you and a lot of other people sign indicating that your software will not do that. You also gave that slip of paper to the FDA to get FDA approval. Later some poor nurse somewhere is prepping the left leg for amputation instead of the right one. The doctor cross checks with the FDA approved software, and verifies that the problem is in the left leg. And . . . do you see where this is going? This too is fraud. And it is criminal in the United States. You WILL be prosecuted.
> And yes, it has happened . . . several times!
Citation?
Citation?
Example of what happens when your medical device just plain doesn't work:
http://www.highbeam.com/doc/1N1-118387E2698885C8.html
Example of what happens when you give 'deal sweeteners' to get your device into a health care facility, or IDN (Integrated Delivery Network):
http://physicianlaw.foxrothschild.com/2009/03/articles/fraud...
Just a couple off the top of my head, many, many more just Lex/Nex it. Or probably better, if you are thinking about getting into this area, PLEASE, talk to your lawyer.
Punishments are generally so harsh because it is considered fraud. The defendants were selling software that didn't work. They either knew it did not work, in which case it is pretty much straightforward fraud, and God help them if someone dies. Alternatively, they did not know that the software did not work. In which case they committed fraud when they represented themselves to the health care organization that purchased the device as being qualified to make a determination as to the efficacy of the software or device. Again, God help them if someone dies.
http://www.highbeam.com/doc/1N1-118387E2698885C8.html
Example of what happens when you give 'deal sweeteners' to get your device into a health care facility, or IDN (Integrated Delivery Network):
http://physicianlaw.foxrothschild.com/2009/03/articles/fraud...
Just a couple off the top of my head, many, many more just Lex/Nex it. Or probably better, if you are thinking about getting into this area, PLEASE, talk to your lawyer.
Punishments are generally so harsh because it is considered fraud. The defendants were selling software that didn't work. They either knew it did not work, in which case it is pretty much straightforward fraud, and God help them if someone dies. Alternatively, they did not know that the software did not work. In which case they committed fraud when they represented themselves to the health care organization that purchased the device as being qualified to make a determination as to the efficacy of the software or device. Again, God help them if someone dies.
The rant on Lifehacker just about sums up my feelings: http://lifehacker.com/5336382/digsby-joins-the-dark-side-use...
"Optional" crapware in the installer just takes advantage of the fact that most people just click through. It's bad and it should be discouraged.
"Optional" crapware in the installer just takes advantage of the fact that most people just click through. It's bad and it should be discouraged.
Either model is hardly innovative.
The installer bundling has been used by the shareware people for ages as an alternative for paying for the application. From recent notable examples - Trillian IM introduced the exact same bundling over a year ago.
The CPU stealing add-on is not exactly an innovation either. The very idea is actually covered by a patent held by a company called Gomez (may be not them, can't remember 100%). The fact that I have to disable it (instead of optionally enabling it) is a reason enough not touch this Digsby thing with a long pole.
Also calling this lovely add-on a "research module" is nothing short of trying to conceal and obscure its real purpose. It is there to generate money by reselling my CPU time. Period. It does not matter if it is not running when the laptop is not plugged in. And I am sure as hell if it was called "let other people use my CPU when it is idle", no one would've enabled it ever. So they are effectively tricking people into using it, which in turn doesn't sit right with me.
The installer bundling has been used by the shareware people for ages as an alternative for paying for the application. From recent notable examples - Trillian IM introduced the exact same bundling over a year ago.
The CPU stealing add-on is not exactly an innovation either. The very idea is actually covered by a patent held by a company called Gomez (may be not them, can't remember 100%). The fact that I have to disable it (instead of optionally enabling it) is a reason enough not touch this Digsby thing with a long pole.
Also calling this lovely add-on a "research module" is nothing short of trying to conceal and obscure its real purpose. It is there to generate money by reselling my CPU time. Period. It does not matter if it is not running when the laptop is not plugged in. And I am sure as hell if it was called "let other people use my CPU when it is idle", no one would've enabled it ever. So they are effectively tricking people into using it, which in turn doesn't sit right with me.
Disclaimer: I work for the company that develops the grid technology Digsby's using, so I suppose I have some bias.
I think Digsby has recognized user's feelings on this issue and their latest update addresses these feelings directly. The new version makes our grid technology apparent to the user. I think the fact they addressed the issue head-on counts for something.
I also feel that it is important for "free" software to find a revenue stream. While there are several examples of truly free software being sustainable, there should also be a place for alternative revenue streams for companies that want to make software available to users at no direct cost.
Yes, users need to know what's going on. This is uber-important. But assuming they do, alternative revenue streams are a good thing for everyone, IMO.
I think Digsby has recognized user's feelings on this issue and their latest update addresses these feelings directly. The new version makes our grid technology apparent to the user. I think the fact they addressed the issue head-on counts for something.
I also feel that it is important for "free" software to find a revenue stream. While there are several examples of truly free software being sustainable, there should also be a place for alternative revenue streams for companies that want to make software available to users at no direct cost.
Yes, users need to know what's going on. This is uber-important. But assuming they do, alternative revenue streams are a good thing for everyone, IMO.
what is this grid technology, and can i supply processing horsepower and get paid?
It is Plura, and while you can technically get paid for it, it's not really worth it for an individual. However, if you can bring hundreds or thousands of computers to the grid by embedding it in an application, then the payments can be significant.
From the Freehacker article I surmise that it's Plura Processing (http://www.pluraprocessing.com/)
"[...] in fact was announced on the Digsby blog as an official way they are going to make some money, with Plura Processing as a partner."
As to whether or not you can supply processing power for a fee, I doubt it. Looking through their individuals page briefly it looks like it's very similar to SETI@home or any other distributed computing effort. If you like the projects they're running you help, if not you don't.
"[...] in fact was announced on the Digsby blog as an official way they are going to make some money, with Plura Processing as a partner."
As to whether or not you can supply processing power for a fee, I doubt it. Looking through their individuals page briefly it looks like it's very similar to SETI@home or any other distributed computing effort. If you like the projects they're running you help, if not you don't.
They pay about $2.50 per CPU at 100% per month. A fraction of the cost of electricity, but lucrative for Digsby.
It's probably hard to sum this up in any law, but what you basically want is for products and services to do exactly what they seem to be designed for, with absolutely no other effects. At the very least, a product with "side effects" wastes time, because you're dealing with details that you shouldn't have to care about. In the worst case, of course, the side effects cause actual harm.
And this isn't limited to PCs; for instance, I'm really annoyed when my gas pump throws up a prompt "do you want a car wash?". Why no, actually; since car washes have absolutely nothing to do with gas pumps, you can safely assume that if I'd wanted a car wash, I would have gone through other channels to request one.
And this isn't limited to PCs; for instance, I'm really annoyed when my gas pump throws up a prompt "do you want a car wash?". Why no, actually; since car washes have absolutely nothing to do with gas pumps, you can safely assume that if I'd wanted a car wash, I would have gone through other channels to request one.
[deleted]
The biggest lie is that Digsby is Free software.
I have been considering building my own home lately and while at the hardware store, i picked up a thick book of home plans. As I flipped through, I realized, this isn't a book of home plans, it's a catalog for plans that you can buy. So I thought, are they selling this? There's nothing in it of value, just pictures of more things that you have to buy later. I looked at the back and sure enough, the catalog itself cost $10 and they dont even have the prices of the home plans themselves. If you want the blue prints for the house, you have to pay MORE money and those cost $60 or more.
And so I started thinking of course, like any hacker would... I've been looking for examples of industries that give away the product of their work. Here was one in architecture and construction. Not only are the blue prints not free, but the catalog of things not free isn't even free. So it's like, two layers of not free in the same industry.
Can you imagine architects giving away their blue prints? Essentially, that's what source code is, it's a blue print for a product. It's an encapsulation of a lot of work, research and development, experimentation, and energy. If architects gave away the blue prints for homes, then architects would have trouble eating.
I know, people say, you can't pay for passion. If people are passionate about software, they'll do it for free. But I'm not so sure that's true. I think there are reasons other than money and passion about software to write software, popularity for example.
Here's the rub, every other popular industry gets money in exchange for their contribution. "If you're good at something, don't do it for free."
Of course I wonder, "Why am I so opposed to Open Source?" Am I insecure about my code? Am I delusional? If so many, seemingly rational people, are pro Open Source, why am I so closed?
It's a real debate inside my head. I don't think it's insecurity. I have no problem writing code that is open and viewable to people who pay me to write it. I would have no problem writing open source code for a company that was paying me to write the code. If it's their code, and they are paying me to write it for them, please, show it to the world -- better for me. I've written enterprise code that never got used outside the company and wished I had something to show people. "I built this badass system for nuclear plants, you should have seen it!" But of course they can't...
I'm just thinking of the logical conclusion... what are the long term consequences of FOSS? I think about incentives here. I think about comparisons between teachers and athletes for example. We say, "We should pay teachers like we pay athletes." I've actually considered being a teacher. Everyone tells me I would be a great one. I really love this stuff. But why should I encourage people to go into a field where I know they will have a tough time eating because there are too many people giving away free labor? How can engineers pay for food if no one is paying them?
Why is this so difficult for me to understand? I'm not stupid. I'm pretty smart. Why doesn't something that seems so obvious to so many other seemingly smart people not make sense to me?
Compare our industry to Medicine and Law. It's actually illegal for people who aren't doctors or lawyer to dispense medical advice or legal advice. These clever professions engineered these laws to protect their industry. Oh, I know lots will cringe at the thought of that. I know the thought is that stuff like this subsidizes crappy coders through artificial scarcity. I'm still not convinced the scarcity is actually scarce, because the production of the product depends on the consumption of scarce products, but I digress...
I think the debate about the flamewar over web programming being stupid is one ramification of this issue. Web programming isn't actually easy. It's easy to a point, just like carpentry is easy to a point and plumbing is easy to a point and electrical work is easy to a point. But it's also easy to be dangerous. It's easy to biuld homes that fall down and plumbing that starts leaking next year and wire a home to catch fire. If you don't have training and education and experience, it's easier to make mistakes.
I see so many people without a background in programming write poorly architected code that performs like a dog and just breaks... it breaks because some wanabe hacker just jumped in and started hacking without knowing wtf (s)he was doing and it ends up costing the company paying for the work more money later on. And you can't blame the consumer. They don't know. They don't know if they give someone their credit card information whether or not that company actually gives a crap about security and if they do, they can actually implement good security protocols. And don't say open source helps with this, because plenty of open source products have huge security holes. I see people complaining all the time about XSS vulnerabilities in word press plugins and with something like that, I could easily write a keylogger that would send your credit card number typed into a wordpress hacked online store right to my database... Probably lots of .cn sites are already doing it...
Anyway, I'll stop ranting now...