3 ms·

Interesting. From my perspective it's the GPLv3 that's the issue. When I'm looking to build something and I see a GPLv3 widget I think "Oh man, so my options wi

by jw14 7y ago

Interesting. From my perspective it's the GPLv3 that's the issue. When I'm looking to build something and I see a GPLv3 widget I think "Oh man, so my options with this will be very limited. I won't be able to do normal things with it." I find Apple's stance slightly odd since I don't think the GPLv3 apps would infect Apple, but then I also haven't taken the trouble to thoroughly understand GPLv3. I started to research it some years ago and my quick conclusion was "avoid". I don't really have too much complaint about GPLv2. It does impose some limits but I feel like I understand them and can work with them. Definitely with you on the $20 microSD card. The markup for storage is absurd. Update: want to add this question. Anyone know why Apple would bar a GPLv3 app from the app store (bash is unfortunate but I think I understand that one)?

kermitismyhero 7y ago
>Update: want to add this question. Anyone know why Apple would bar a GPLv3 app from the app store (bash is unfortunate but I think I understand that one)? I think it's simply a company-wide policy made at the recommendation of overly-cautious legal counsel. On the matter of GPLv3, I think this is going to be an "agree to disagree" type of thing. I actually quite like the changes over v2. But then I'm not a professional developer. I'm just a bookkeeper who dabbles in coding for fun and for a bit of ad-hoc automation on the job. My perspective is certainly quite different from someone who makes a living programming.
- jw14 7y ago
  Glad this didn't turn into a flame war. I like the idea of sharing everything in theory but I don't yet see how to make a living without putting a price tag on something. Working as a contractor writing closed source software and allowing my clients to mostly own what I create allows me to work around 30 hours a week and spend time doing volunteer work. If there was a path to do that with Free Software I might go for it.
m463 7y ago
I've wondered about it, and I suspect it's either the tivo part (you can't restrict the code from running), or the patent clause. It's ironic because apple is actually violating gplv2 with bash (it should distribute rootless.h)

by jw14 7y ago

kermitismyhero 7y ago

>Update: want to add this question. Anyone know why Apple would bar a GPLv3 app from the app store (bash is unfortunate but I think I understand that one)? I think it's simply a company-wide policy made at the recommendation of overly-cautious legal counsel. On the matter of GPLv3, I think this is going to be an "agree to disagree" type of thing. I actually quite like the changes over v2. But then I'm not a professional developer. I'm just a bookkeeper who dabbles in coding for fun and for a bit of ad-hoc automation on the job. My perspective is certainly quite different from someone who makes a living programming.

jw14 7y ago
Glad this didn't turn into a flame war. I like the idea of sharing everything in theory but I don't yet see how to make a living without putting a price tag on something. Working as a contractor writing closed source software and allowing my clients to mostly own what I create allows me to work around 30 hours a week and spend time doing volunteer work. If there was a path to do that with Free Software I might go for it.

m463 7y ago

I've wondered about it, and I suspect it's either the tivo part (you can't restrict the code from running), or the patent clause. It's ironic because apple is actually violating gplv2 with bash (it should distribute rootless.h)