Again, you think, and your wrong. Read the developer papers on OS X before assuming because your assumptions have no basis in fact.
http://developer.apple.com/mac/libra...TP40008898-SW1
Again, you think, and your wrong. Read the developer papers on OS X before assuming because your assumptions have no basis in fact.
http://developer.apple.com/mac/libra...TP40008898-SW1
Last edited by deanjo; 08-29-2009 at 11:02 AM.
As someone who has worked under all of those licenses I have every right to be negative about them. If I had my way, everything would be public domain.
Code is nothing but a form of math. Imagine what the world would be like if someone put restrictions on the ability to add 2+2.
Last edited by deanjo; 08-29-2009 at 11:12 AM.
It is, I just said you are not convincing by using your right. Especially you.
With words is easy, your attitude though with the people/software/licenses which at least try to do that, says the opposite.If I had my way, everything would be public domain.
Oh I couldn't agree more, but that's exactly what the proprietary software, that you defend, does. Because of that they got an X bigger than OSX's one from me.Code is nothing but a form of math. Imagine what the world would be like if someone put restrictions on the ability to add 2+2.
And I have to disagree with you. If I put out code free of any restrictions my goal is to benefit the end user, not political agendas. If someone wants to use my code and want's to slap it in a proprietary app so be it. This philosphy has worked well for sqlite which is everywhere and the end result is everybody gains.
So you want to benefit the end user without adding restrictions. Nice and welcome. But the restrictions your code will have when someone uses it for its proprietary app don't matter? Are they for the genearl benefit? Like that you produce much more restrictions than you intented to do when you offered the code without any at all.