4 ms·
> AFAIK, you have to pay a yearly fee for the privilege of doing so. That hasn't been the case for a number of years. As long as you have a Mac, you can downlo
by kn0where 9y ago
> AFAIK, you have to pay a yearly fee for the privilege of doing so.
That hasn't been the case for a number of years. As long as you have a Mac, you can download Xcode for free, compile an app, and sync it over to your iOS device.
- ariwilson 9y agoSuper simple to do as an end user, for sure.
- bobwaycott 9y agoYour average end user who requires things to be simple is never going to install their own apps outside the approved, simple channels.
- Larrikin 9y agoThere are multiple thriving app stores in the global android market
- wil421 9y agoI’ll take one App Store over many anyday if it severely lessons the chance of getting malware.
- racer-v 9y agoWould you also take one news source over many if it lessens the chance of seeing "fake news"?
- dymk 9y agoWould you take one false equivalency over another if it lessens the chance of an "ironic reply"?
- racer-v 9y agoChoosing your app store and choosing your news source aren't equivalent, but they're both desirable (for related reasons).
- JumpCrisscross 9y ago> Would you also take one news source over many if it lessens the chance of seeing "fake news"? Yes. This is why, every morning, I first get my news from trusted sources.
- racer-v 9y agoWho picks those sources - you or your phone's operating system vendor?
- bobwaycott 9y agoYou are not replying to my meaning or intention. The context of the discussion was clear. You’ve taken it in a wholly different direction.
- ekianjo 9y agoNeeding a Mac is an extra expense in itself. I fail to see much difference.
- futhey 9y agoSure. A company doesn't choose to spend hundreds of thousands or millions of dollars per year to port their development tools to a third-party platform. I'm sure if they believed they would get more & higher quality developers to build apps by doing so, they already would have. Makes since, especially since Windows historically hasn't done the same for Visual Studio / C# (I know they're supposedly trying now or planning to but I confess I haven't followed along closely enough to determine if it's cancelled, delayed, or the scope was actually smaller than full dot net + c# support).