Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Phillip McMahon <phillip.mcmahon@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Andrew Fried <afried@spamteq.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Should we sunset Windows 7 support?
Date: Thu, 12 Nov 2020 09:46:32 +0100	[thread overview]
Message-ID: <CABtXGiCs1fS3FHAwHL1zohuL1BfDhY7GhZhtLFfiqS2aJstr3g@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pmKxGYmxxs0pLt=zt2igy6aR-g5xsB=2Zew6oWVY0Z3w@mail.gmail.com>

Take a look here

https://gs.statcounter.com/os-version-market-share/windows/desktop/worldwide

Would seem to suggest Windows 7 is in decline but still represents
around 25% of OS footprint out there.

On Thu, 12 Nov 2020 at 09:39, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hi Andrew,
>
> On Thu, Nov 12, 2020 at 9:29 AM Andrew Fried <afried@spamteq.com> wrote:
> >
> > We recently began deploying clusters of recursive DNS "firewalls" that
> > use wireguard to secure and authenticate all traffic between the client
> > and servers.   What we quickly learned was that virtually the entire
> > customer base in India uses Windows 7 almost exclusively.
> >
> > I can certainly understand the desire to streamline development and
> > focus on current versions of client operating systems, but by
> > deprecating support for Windows 7 you would be reducing the number of
> > potential Wireguard deployments by hundreds of millions of users,
> > particularly in Asian and underpopulated communities in Africa.  Most of
> > the end users there simply can't afford the cost of updating to the
> > latest version of Windows.  I personally wish this were not the case,
> > but it is what it is.
>
> Thanks for that info. This is by far the most compelling point brought
> up so far and is one likely to keep us supporting Windows 7 for some
> time. I assume your deployment to those parts of the world is quite
> large?
>
> Are there any websites or other sources you used to find these
> statistics about usage per region? It sounds like that'd be useful to
> look at.
>
> Jason



-- 
Use this contact page to send me encrypted messages and files

https://flowcrypt.com/me/phillipmcmahon

P.S. Drowning in email? Try SaneBox and take back control:
http://sanebox.com/t/old3m. I love it.

  reply	other threads:[~2020-11-12  8:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 12:27 Jason A. Donenfeld
2020-11-10 12:47 ` Laslo Hunhold
2020-11-10 12:56   ` samuel.progin
2020-11-10 13:06     ` Jason A. Donenfeld
2020-11-10 12:57 ` Isaac Boukris
2020-11-10 15:06 ` Reiner Karlsberg
2020-11-12  8:34   ` Jason A. Donenfeld
2020-11-12  9:13     ` Roman Mamedov
2020-11-10 17:38 ` Andrew Fried
2020-11-12  8:38   ` Jason A. Donenfeld
2020-11-12  8:46     ` Phillip McMahon [this message]
2020-11-12  8:50       ` Jason A. Donenfeld
2020-11-12  9:03       ` Berge Schwebs Bjørlo
2020-11-13  2:56         ` Jeffrey Walton
2020-11-19 16:59           ` Jason A. Donenfeld
2020-11-19 17:16             ` akloster
2021-10-07 23:35             ` Jason A. Donenfeld
2020-11-12 21:56   ` Panagiotis Kalogiratos
2020-11-12 17:38 ` Jeffrey Walton
2020-11-12 17:42   ` Phillip McMahon
2020-11-12 18:11   ` Neal Gompa

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=CABtXGiCs1fS3FHAwHL1zohuL1BfDhY7GhZhtLFfiqS2aJstr3g@mail.gmail.com \
    --to=phillip.mcmahon@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=afried@spamteq.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).