Response to “WireGuard: great protocol, but skip the Mac app”
This appears to be a very typical response from an Apple user who doesn&#x27;t understand the lengths and hoops developers have to jump through to work around Apple&#x27;s many, many restrictions, bugs and limitations.<p>In my day job, our Apple developers have spent years finding solutions to iOS restrictions around CallKit, Push Notifications and NSTodaysProblem, and those are just the things Apple has intentionally restricted, once you get into the bugs and poor documentation for some APIs it&#x27;s another story.<p>If our users knew the half of what our Apple Developers have to do, the meetings, discussions, concessions and re-design that has to be done to make things just work, even on par with the Android equivalent, they might be a little bit more understanding.<p>WireGuard has been excellent, and as a Linux user, I haven&#x27;t needed an app, I have a couple of aliases in my shell to start and stop my tunnels. I&#x27;ve used WireGuard daily for work since lockdown and I used it daily for personal use, while commuting to work before lockdown. In all of that time, I&#x27;ve never had a single issue due to WireGuard (and there isn&#x27;t even a Linux app to be seen). The expectation is often different between Linux and Apple users though.<p>When I was setting up for the first time, Jason even found time to help me himself on the IRC channel, something I&#x27;ve never expected, and for which I am eternally grateful.<p>I made a donation to WireGuard last year, I&#x27;ll be doing the same this year and I encourage others to &quot;put their money where their mouth is&quot; and show a little support for the people making and sharing this software for free. I expect an Apple user can afford a small cut of their or their employer&#x27;s money to do so.