From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] USB3 or HDMI ethernet? - Are wires dead?
Date: Mon, 18 Apr 2016 19:35:25 +0300 [thread overview]
Message-ID: <BB88E4B7-2110-4F13-B059-4C3EAEF176AB@gmail.com> (raw)
In-Reply-To: <CAA93jw47yqrETEjC0w-5MFf+PA1q1FfP7LzEdG_zq2HtRMRX4w@mail.gmail.com>
> On 18 Apr, 2016, at 17:50, Dave Taht <dave.taht@gmail.com> wrote:
>
> But it asks a question - if basic wifi-only + compute has fallen so low, is ethernet dead?
Among the serious PC gaming community, it’s widely recognised that wired links (both LAN and WAN) have much lower latency and packet loss than wireless ones. In competitive multiplayer games, this is a serious matter, especially when “competitive multiplayer” is ascended to “eSports”.
That community is one that obsesses about scan and poll frequencies on their keyboards and mice, refresh rates and display latencies on their monitors, and all that jazz. You won’t convince them to switch to Wifi for their main battlestation, *even if* the present bloat problems are fixed. They’ll tolerate it for a laptop on which they do their homework, that’s all.
However it is also true that for a certain type of low-end user, “wireless” operation is “simpler” and “neater”, no matter what form it takes. They hardly even notice any performance problems that come with it, or accept them as a fact of life with "newfangled technological thingamajigs”.
- Jonathan Morton
next prev parent reply other threads:[~2016-04-18 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 14:50 [Cerowrt-devel] " Dave Taht
2016-04-18 16:08 ` Michael Richardson
2016-04-18 16:14 ` Luis E. Garcia
2016-04-18 16:32 ` Dave Taht
2016-04-18 16:35 ` Jonathan Morton [this message]
2016-04-18 18:03 ` [Cerowrt-devel] [Bloat] " Aaron Wood
2016-04-18 23:10 ` [Cerowrt-devel] " Dave Taht
2016-04-19 17:51 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BB88E4B7-2110-4F13-B059-4C3EAEF176AB@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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