1. 47

  2. 5

    Sorry it feels like wasted time, but you wrote up some really interesting techniques so it was worthwhile for your readers!

    1. 3

      Thanks! I seem to get that message a lot for this post, glad I shared something useful ^_^

    2. 3

      This is simultaneously an awesome writeup showcasing lots of cool tools and workflows, and also one of the biggest reminders of why I can never use MacOS (and I’ve tried many a time, including being required to use it at work for a year once): it just constantly reminds me that Apple owns the device, not me, and punishes those who try to step outside Apple’s blessed happy paths.

      1. 10

        that Apple owns the device

        This is disingenuous BS. Apple isn’t paywalling access to this API or remote controlling your machine through this API. It’s just a private API. You have every right to disagree with Apple’s design decisions, but “Apple owns the device, not me” is a gigantic leap from “I don’t like this.”

        1. 1

          Maybe “owns the experience of the device” is a more accurate wording, and to be fair, my opinions here are colored by years of constant frustration fighting the various ways MacOS fights developers who try to step outside aforementioned “happy path”, often in changing ways across OS releases, that perpetually reinforce this view.

      2. 2

        Really interesting write up. As a regular user, it’s nice to see the defensive in depth Apple put into macOS. As a developer… this is why we can’t have nice things. Being able to innovate and do things the OS wasn’t designed to do makes for a much richer ecosystem. Unfortunately, things are getting so locked down we are getting limited to only things Apple has envisioned and their APIs have a lot of bugs. Occasionally my window manager ends up not knowing where the bounds of the monitor are until I reboot. I have no hope this will ever be fixed.