Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Lewis Donzis <>
To: "Jason A. Donenfeld" <>
Cc: Bruno <>,
Subject: Re: MacOS app update needed
Date: Thu, 22 Sep 2022 07:04:09 -0500 (CDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

----- On Sep 22, 2022, at 6:43 AM, Jason A. Donenfeld wrote:
> On Wed, Sep 21, 2022 at 10:22 AM Bruno <> wrote:
>> Hi,
>> Windows Client project don't feel alive either. Last commit has 6 months
>> and last release is 9 month old.
>> Same, here and here
>> Version 0.5.3 works well, but I suppose it can be even better!
> That seems pretty uncalled for. Folks asking for a wireguard-apple
> update have good reason to do so -- there are outstanding bugs and
> pull requests. But for wireguard-windows/wireguard-nt? C'mon now --
> that's received some *extremely* active development, stabilizing after
> nearly weekly updates for some time. Are there outstanding pull
> requests for it? So your note here really isn't appreciated. The
> WireGuard project doesn't churn out code and updates just for the sake
> of writing code and doing updates. Things need to have rationale.
> There will be updates to wireguard-windows/wireguard-nt at some point
> when development makes sense there. But right now? Is there something
> pending? Instead maybe be thankful that that software has reached a
> point of stability where project development energies can go into more
> pressing tasks, such as wireguard-apple.
> Jason

I could not agree more.  What a world we live in where code that hasn't been touched for a few months is considered stale, rather than being rewarded and appreciated for reliability and stability.  Jason, congratulations on not needing to touch that code for six months!  Much of the beauty of Wireguard is its simplicity, to the point that it can be done "right", and it really shouldn't need to be touched!

  reply	other threads:[~2022-09-28 10:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21  7:28 Simon Karberg
2022-09-21  7:52 ` Houman
2022-09-21  8:20   ` Bruno
2022-09-22 11:29     ` Harald Dunkel
2022-09-22 11:34       ` Jason A. Donenfeld
2022-09-22 11:43     ` Jason A. Donenfeld
2022-09-22 12:04       ` Lewis Donzis [this message]
2022-09-22 13:26         ` Bruno
2022-09-22 13:49           ` Jason A. Donenfeld
2022-09-22 11:33   ` Jason A. Donenfeld
2022-09-22 11:48 ` Jason A. Donenfeld
2022-09-24  1:28   ` Ken Case

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).