1,515 karma · joined November 22, 2013
[ my public key: https://keybase.io/oddevan; my proof: https://keybase.io/oddevan/sigs/jUdMqiarv-f7aKiTLRaaC4nwtmlobOZnMjLbNcKVpdo ]
This line was probably required to get some manager at Apple to sign off on this. There are few companies as protective of their trademarks--their _name_--as Apple, and they probably wanted to make sure that an accidental commit from a developer that included an Apple logo or the word 'iPhone' didn't cause irreparable damage to their trademark.
Valid fear? That's debatable. But I'd rather have a company add _one line_ to an already minimal license than not open source at all out of this fear.
I thought the way it worked is: - User buys game on 3DS, links to their Nintendo account, can play on 3DS, iOS, and Android. Nintendo gets $10. - User buys game on iOS, links to their Nintendo account, can play on 3DS, iOS, and Android. Apple gets $3, Nintendo gets $7 - User buys game on Android, links to their Nintendo account, can play on 3DS, iOS, and Android. Google gets $3, Nintendo gets $7
And that's the crux there. It's not always malicious (I want to make a proprietary extension and sell it), sometimes it's a fact of the environment (I have to link this against a proprietary library in order to deploy to this hardware). Some will say "find a new environment that isn't developer-hostile", and others will say "find code that doesn't impose those restrictions." It's not black-and-white.
I have the greatest respect for RMS and the FSF. I compromise on my freedom as a developer all the time; I know that. But thanks to the ideals that RMS puts forth, I know that I'm compromising. I know what the risks are to using BSD instead of GPL, and so I weigh those risks.
So yeah, I could have made my point a little better. Here's some elaboration:
I will personally avoid applying the GPL, either by my own decision or because of code I am using, mostly because I want the freedom, both for myself and for those who might use my code, to release on iOS.
That being said, this doesn't seem to be about a company looking at the GPL and avoiding it. This looks like a company looking at the GPL, not complying with its restrictions, but using the code anyway.
I may not like the GPL, but if a fellow developer decides to use it, I will defend that right.
[edited to elaborate on my reasons for not using the GPL. See comments below]
I know that any system is only as strong as its weakest link, so anytime I use my normal card I'm still at risk of whatever retailer I'm at getting hacked, but I figure that the more I use the EMV chip or Apple Pay, the more my card company and the retailers know there's another person out there that cares about this sort of stuff and thus one more reason to invest in the more secure POS terminals.
(4 happens anyway; I get a notification whenever my card is used, whether it's the card or the phone)
If you're keeping any significant portion of your existing workforce, absolutely. Doing a single round of layoffs and then being able to tell the remaining employees "If we haven't talked to you, you're staying" can make the hit to morale that much smaller. It'll still lower morale, that's unavoidable. But it will take away the stress of "is my job safe?" for the remaining employees.
> Because it has no benefit for you, only for the company.
Really?! Making a tool you use every day better has no benefit for you? Sure, I can build my own text editor if I really wanted to, but I'd rather send a bug report to BBEdit to fix a problem in an otherwise good product.
I immediately concluded that being in a publicly traded company is boring. I work for a school now. :)
Got one for Christmas. Bought a case and a second one since. I knew it'd get outspecc'd someday, just wasn't expecting it THIS soon...
In other words: the flash cards are most useful to him in his carry-on so he can study while waiting for/during his flight. Putting them in his checked baggage (assuming he even checked a bag) would defeat the purpose.