Live data from Hacker News

Response to “WireGuard: great protocol, but skip the Mac app”

lists.zx2c4.com

1–10 of 392 posts

Re: Response to “WireGuard: great protocol, but skip the Mac app”

#6
post #4

May I suggest to @dang to update the title with something just a little bit more informative without much editorialization, like: WireGuard Developer Response to "Great protocol, skip the Mac app" blogpost

Mods don't/can't read every comment posted 24/7, and don't actually get pinged if you put an @ before their name. Best way to actually contact the moderation staff is to send an email to hn@ycombinator.com

Note that it is currently 1:33 AM on the west coast, so they may not see it for a number of hours.

Re: Response to “WireGuard: great protocol, but skip the Mac app”

#7
This appears to be a very typical response from an Apple user who doesn't understand the lengths and hoops developers have to jump through to work around Apple's many, many restrictions, bugs and limitations.

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's another story.

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.

WireGuard has been excellent, and as a Linux user, I haven't needed an app, I have a couple of aliases in my shell to start and stop my tunnels. I'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've never had a single issue due to WireGuard (and there isn't even a Linux app to be seen). The expectation is often different between Linux and Apple users though.

When I was setting up for the first time, Jason even found time to help me himself on the IRC channel, something I've never expected, and for which I am eternally grateful.

I made a donation to WireGuard last year, I'll be doing the same this year and I encourage others to "put their money where their mouth is" 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's money to do so.

Re: Response to “WireGuard: great protocol, but skip the Mac app”

#9

This appears to be a very typical response from an Apple user who doesn't understand the lengths and hoops developers have to jump through to work around Apple's many, many restrictions, bugs and limitations. 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…

I'm not sympathetic. If you don't think you can do a good job at something due to factors outside your control, you can choose to not do it (refuse to support mac) or do a subpar job. If you choose the latter don't be surprised if users give you negative reviews. There's no participation trophies in business.

Re: Response to “WireGuard: great protocol, but skip the Mac app”

#10

This appears to be a very typical response from an Apple user who doesn't understand the lengths and hoops developers have to jump through to work around Apple's many, many restrictions, bugs and limitations. 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…

> This appears to be a very typical response from an Apple user who doesn't understand the lengths and hoops developers have to jump through to work around Apple's many, many restrictions, bugs and limitations.

Eh? Isn't that a description of the original complaint, and the 'a response' submitted here is from WireGuard creator/lead Jason/zx2c4 explaining much as you do the restrictions, bugs, and limitations he's tried to work around?

Post reply on HN