develwoutacause’s avatardevelwoutacause’s Twitter Archive—№ 1,157

      1. Can we take a moment to acknowledge how ridiculous it is that @Apple has ~zero support for developer tools running outside their own products? If a developer wants to support Apple users, they must *themselves* buy Apple products. WTF?
        Permalink On twitter.com Twitter logo develwoutacause’s avatar ❤️ 2 Favorites Mood -3 🙁
    1. …in reply to @develwoutacause
      Motivating example: I have a website, it has a bug on #iOS. I want to fix said bug. I have a #Windows / #Linux machine. I cannot open an inspector on this iOS device. There is no official solution to this problem. Some workarounds exist, but these only work for old versions.
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +1 🙂
  1. …in reply to @develwoutacause
    You're supposed to use #Safari to open an inspector on your device, but I can't install Safari because I'm on Windows. I remember when Safari used to support Windows, but apparently that's just gone now. support.apple.com/en-us/HT204416#:~:text=Update%20Safari%20on%20Windows%20PC
    On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
    1. …in reply to @develwoutacause
      There's inspect.dev/ which seems cool and does support "inspect iOS from Windows", but it's not official and is a paid product.
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +3 🙂
      1. …in reply to @develwoutacause
        I could run an iOS simulator, though simulators/emulators are never perfect recreations. However the official simulator requires #XCode which, you guessed it, only runs on #Mac. developer.apple.com/documentation/xcode/running-your-app-in-the-simulator-or-on-a-device
        Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +3 🙂
        1. …in reply to @develwoutacause
          #Microsoft #Xamarin does support a simulator, but it needs a remote #Mac host to do so. docs.microsoft.com/en-us/xamarin/tools/ios-simulator/ My understanding is that @Apple, either by technical laziness or explicit policy, require that their dev tools only run on Apple products, which handcuffs 3P vendors.
          Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +2 🙂
          1. …in reply to @develwoutacause
            Only other option is to install #Mac in a virtual machine, but even that violates #macOS terms of service which allow running in a VM *only* if the host is on Apple hardware. apple.com/legal/sla/docs/macOS1013.pdf
            A screenshot of the macOS terms of service. It has the following text highlighted "you are granted a limited, non-transferable, non-exclusive license: ... to install ... on each Mac Computer you own or control that is already running the Apple Software".
            Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood -1 🙁
            1. …in reply to @develwoutacause
              AFAICT, there is no viable, @Apple-approved way of developing and supporting for Apple devices *without* purchasing Apple products. If that isn't the *definition* of #monopoly, I don't know what is.
              Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood 0
              1. …in reply to @develwoutacause
                And this only hurts @Apple's own users. I can't fix this bug, therefore anyone viewing my website on #iOS devices will feel the pain of the bug. I'm not going to spend $1,300 on an #iMac to debug my personal website. @Apple's choice here directly harms it's own users.
                Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood -6 🙁