From: Jonathan Morton <chromatix99@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: "aqm@ietf.org" <aqm@ietf.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] Bufferbloat and the policy debate on packet loss in nanog
Date: Mon, 2 Mar 2015 03:19:41 +0200 [thread overview]
Message-ID: <CAJq5cE1NPqOH1qvZM16NoDcxVJtCRFc7Bi40ok1GwotgU+h0ew@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-PSfeHnkgNFCwQzbDhTRDt2-vihNsuydcVNLNmMX_G7YQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
And the reason for that, of course, is that "pile 'em high and sell 'em
cheap" works pretty well in the consumer marketplace - something that Far
Eastern companies have capitalised on a great deal. Amortising a not
inconsiderable R&D cost over the largest possible number of units makes
economic sense.
I think we'd all just rather they sorted out a better design in that
initial R&D phase. That's something that doesn't appeal to the mindsets of
most of those Far Eastern countries very well. Japan is the most likely
exception, but only because they tend to make stuff for themselves first
and others second.
Funny story from the early days of the Raspberry Pi: they were using a
Chinese factory because they needed cheap, and didn't really know how many
would sell - ten thousand was hoped for, as that would break even quite
nicely. But they went to a lot of trouble to be sure of getting something
that actually worked back from them. Engineering samples had come back to
the UK and tested fine, at last, so they gave the green light.
Then the first batch of 2000 Pis arrived, and the Ethernet port didn't work
on a single one of them. The factory had swapped out the RJ45 socket for a
cheaper one after completing the engineering samples, without noticing that
it didn't have the integrated magnetics that the design relied on, and as a
consequence also had a completely incompatible pinout. They quickly learned
their lesson on that point when the batch was sent back for repair, which
entailed hand desoldering and resoldering to swap the socket for the
correct one. That alone probably tripled the factory's costs, even at Asian
labour rates, but it was their own fault. Penny wise...
Of course the Pi sold slightly better than predicted, so they were soon
able to find a factory in Wales that fitted the budget.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 2009 bytes --]
next prev parent reply other threads:[~2015-03-02 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 23:22 [Cerowrt-devel] " Dave Taht
2015-03-02 0:56 ` [Cerowrt-devel] [Bloat] " Aaron Wood
2015-03-02 1:10 ` Jim Gettys
2015-03-02 1:19 ` Jonathan Morton [this message]
2015-03-02 12:26 ` [Cerowrt-devel] " dpreed
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=CAJq5cE1NPqOH1qvZM16NoDcxVJtCRFc7Bi40ok1GwotgU+h0ew@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=woody77@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