Comment Why do painters paint? (Score 1) 104
>I don't think free software will stay in the
>hands of purely unpaid volonteers forever.
"Unpaid volunteers"?! It's all you think programmers with free time are? Troll!! I don't try to understand women, and would never try to understand programmers/geeks. Yes we do work for 8 hours in front of a computer, and when we get home what we do? More computer time!
If I help develop open software it's not just because I'm a "volunteer" for the open source movement, it's far more than that. Sometimes just plain curiosity:
- "let's check how this dude did that function" Hey, it's wrong, if I change this two lines of code the routine will be a lot faster. And let's write an e-mail with thanks to the author for this great program and with this code correction.
Sometimes is the "and if". You're using a program, ang think: "AND IF the program could do X thing automatically?". Then you open the code and implement some feature that the author didn't planned/needed, and voila, a better program.
And once a year, you use a program and it doesn't work with that videocard or HD driver, then you strech-a-itchy and make the thing work.
And a lot more different reasons can make someone collaborate with the authors to improve a program, because it's fun, because it's cool, because have nothing to do on sundays, and none of the reasons above are related to money.
>hands of purely unpaid volonteers forever.
"Unpaid volunteers"?! It's all you think programmers with free time are? Troll!! I don't try to understand women, and would never try to understand programmers/geeks. Yes we do work for 8 hours in front of a computer, and when we get home what we do? More computer time!
If I help develop open software it's not just because I'm a "volunteer" for the open source movement, it's far more than that. Sometimes just plain curiosity:
- "let's check how this dude did that function" Hey, it's wrong, if I change this two lines of code the routine will be a lot faster. And let's write an e-mail with thanks to the author for this great program and with this code correction.
Sometimes is the "and if". You're using a program, ang think: "AND IF the program could do X thing automatically?". Then you open the code and implement some feature that the author didn't planned/needed, and voila, a better program.
And once a year, you use a program and it doesn't work with that videocard or HD driver, then you strech-a-itchy and make the thing work.
And a lot more different reasons can make someone collaborate with the authors to improve a program, because it's fun, because it's cool, because have nothing to do on sundays, and none of the reasons above are related to money.
