3 ms·

> solely because of Apple’s policies. It really isn’t this.

by zepto 6y ago

kactus 6y ago
Please elaborate.
- zepto 6y ago
  I love iPads - I have used one almost every day since they were first released. But.. they just aren’t great for the same kinds of professional software that works well on the desktop. It’s not about Apple’s policies. It that the Mac is just better for desktop style apps for obvious reasons. I do think that this can be overcome in the end by really figuring out how to design for the platform, but we are nowhere near that today. I have bought various editors including Coda, and I also bought prompt (which Panic is still working on). I use prompt regularly for impromptu server maintenance or quick diagnostics, but I never use the editors. This is all about what the devices are good for and nothing to do with policies.
  - smoldesu 6y ago
    Either way, the original comment was arguing that the limitations in place are entirely arbitrary, and their argument still rings true. Apparently, the iPhone worked just fine as a code editor: as they mention in the article, the primary technical hurdle was the Javascript engine, which was forced to use Apple's gimped WebKit offerings instead of a real browser engine.
    - zepto 6y ago
      > Either way, the original comment was arguing that the limitations in place are entirely arbitrary, No, the original comment argued that the limitations are the only reason a class of professional software is not successful on iOS, which is certainly false. > Apparently, the iPhone worked just fine as a code editor Obviously it doesn’t work as well as a Mac. Few people would choose to edit code on an iPhone where a Mac or Linux machine was available instead, so no it doesn’t ‘work just fine’.
appleausssse 6y ago
It really is, and the problem is ubiquitous across app categories. Here's another example: you cannot selectively block JavaScript in an iOS browser. On Android/MacOS/Windows/Linux, you can use a browser extension like Noscript to only run trusted or necessary JS. Safari only provides a coarse on/off toggle, and Apple forbids any browser that does not use their proprietary WebKit framework. None of the App Store content blockers allow seamless fine-grained control like every other platform supports.
- zepto 6y ago
  None of this has anything to do with why the iPad and iPhone are not good for desktop style professional apps. You list a bunch of ‘examples’ - but what are they examples of? Nobody disputes that Apple controls iOS.
  - appleausssse 6y ago
    They are examples of how Apple's policy decisions stifle competition and result in a worse product for consumers. Apple's devices cannot adequately protect my privacy, because of their efforts to prevent competitors from making products in any of the markets that they participate in.
    - zepto 6y ago
      > They are examples of how Apple's policy decisions stifle competition and result in a worse product for consumers. No they aren’t. They are just statements about iOS’s design. You don’t make any case for how they make a anything worse. > Apple's devices cannot adequately protect my privacy, because of their efforts to prevent competitors from making products in any of the markets that they participate in. This paragraph is gibberish. You might want to edit it.

> solely because of Apple’s policies. It really isn’t this.

by zepto 6y ago

> solely because of Apple’s policies. It really isn’t this.

kactus 6y ago

Please elaborate.

zepto 6y ago
I love iPads - I have used one almost every day since they were first released. But.. they just aren’t great for the same kinds of professional software that works well on the desktop. It’s not about Apple’s policies. It that the Mac is just better for desktop style apps for obvious reasons. I do think that this can be overcome in the end by really figuring out how to design for the platform, but we are nowhere near that today. I have bought various editors including Coda, and I also bought prompt (which Panic is still working on). I use prompt regularly for impromptu server maintenance or quick diagnostics, but I never use the editors. This is all about what the devices are good for and nothing to do with policies.
- smoldesu 6y ago
  Either way, the original comment was arguing that the limitations in place are entirely arbitrary, and their argument still rings true. Apparently, the iPhone worked just fine as a code editor: as they mention in the article, the primary technical hurdle was the Javascript engine, which was forced to use Apple's gimped WebKit offerings instead of a real browser engine.
  - zepto 6y ago
    > Either way, the original comment was arguing that the limitations in place are entirely arbitrary, No, the original comment argued that the limitations are the only reason a class of professional software is not successful on iOS, which is certainly false. > Apparently, the iPhone worked just fine as a code editor Obviously it doesn’t work as well as a Mac. Few people would choose to edit code on an iPhone where a Mac or Linux machine was available instead, so no it doesn’t ‘work just fine’.

appleausssse 6y ago

It really is, and the problem is ubiquitous across app categories. Here's another example: you cannot selectively block JavaScript in an iOS browser. On Android/MacOS/Windows/Linux, you can use a browser extension like Noscript to only run trusted or necessary JS. Safari only provides a coarse on/off toggle, and Apple forbids any browser that does not use their proprietary WebKit framework. None of the App Store content blockers allow seamless fine-grained control like every other platform supports.

zepto 6y ago
None of this has anything to do with why the iPad and iPhone are not good for desktop style professional apps. You list a bunch of ‘examples’ - but what are they examples of? Nobody disputes that Apple controls iOS.
- appleausssse 6y ago
  They are examples of how Apple's policy decisions stifle competition and result in a worse product for consumers. Apple's devices cannot adequately protect my privacy, because of their efforts to prevent competitors from making products in any of the markets that they participate in.
  - zepto 6y ago
    > They are examples of how Apple's policy decisions stifle competition and result in a worse product for consumers. No they aren’t. They are just statements about iOS’s design. You don’t make any case for how they make a anything worse. > Apple's devices cannot adequately protect my privacy, because of their efforts to prevent competitors from making products in any of the markets that they participate in. This paragraph is gibberish. You might want to edit it.