From: Patrick Maupin <pmaupin@gmail.com>
To: esr@thyrsus.com
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] Build vs. modify vs. what should we be doing anyway?
Date: Mon, 12 Mar 2012 16:45:45 -0500 [thread overview]
Message-ID: <CAPz3yKeHEK3JOq3YWHSzAsQ71-U=f_0ybVgonPy39H5SW5vnFg@mail.gmail.com> (raw)
In-Reply-To: <20120312213723.GD17895@thyrsus.com>
On Mon, Mar 12, 2012 at 4:37 PM, Eric S. Raymond <esr@thyrsus.com> wrote:
> Good point. Then, though, we're dealing with the risk that our supplier
> will EOL the product we're blue-wiring. I can tell you from experience
> that consumer-grade GPSes like these have ridiculously short lifetimes.
Which is why the most important thing is to get the process down of
identifying what works and be able to vet a new device quickly. As I
explained in my original posting, even high-dollar modules can get
EOLed, and then you're out money on your PCB blanks. The only other
alternative is to pick a reasonable build size and always build that
many at a time. But the problem with that batch mode is that you're
either carrying a lot of (more expensive than $23/unit) inventory, or
you're always out of stock when somebody wants one, or (more likely)
you oscillate between those two states.
next prev parent reply other threads:[~2012-03-12 21:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:02 Patrick Maupin
2012-03-12 21:03 ` Eric S. Raymond
2012-03-12 21:18 ` tz
2012-03-12 21:26 ` Eric S. Raymond
2012-03-12 21:28 ` Patrick Maupin
2012-03-12 21:39 ` Eric S. Raymond
2012-03-12 22:10 ` Patrick Maupin
2012-03-12 22:23 ` tz
2012-03-12 22:33 ` Patrick Maupin
2012-03-13 2:29 ` Ron Frazier (NTP)
2012-03-13 2:39 ` Chris Kuethe
2012-03-12 22:45 ` Eric S. Raymond
2012-03-12 23:01 ` Dave Taht
2012-03-13 1:43 ` Eric S. Raymond
2012-03-13 2:04 ` Chris Kuethe
2012-03-13 2:13 ` Eric S. Raymond
2012-03-13 2:40 ` Dave Taht
2012-03-13 2:53 ` Chris Kuethe
2012-03-13 4:54 ` Eric S. Raymond
2012-03-13 13:23 ` Dave Taht
2012-03-13 14:35 ` tz
2012-03-13 16:04 ` Eric S. Raymond
2012-03-13 16:22 ` tz
2012-03-13 2:38 ` Ron Frazier (NTP)
2012-03-13 2:42 ` Chris Kuethe
2012-03-13 3:00 ` Ron Frazier (NTP)
2012-03-13 3:04 ` Dave Taht
2012-03-13 3:06 ` Chris Kuethe
2012-03-13 3:16 ` Dave Taht
2012-03-13 3:31 ` Chris Kuethe
2012-03-13 4:49 ` Dave Taht
2012-03-13 4:55 ` Eric S. Raymond
2012-03-13 4:16 ` Eric S. Raymond
2012-03-12 21:40 ` tz
2012-03-12 21:27 ` Patrick Maupin
2012-03-12 21:22 ` Patrick Maupin
2012-03-12 21:37 ` Eric S. Raymond
2012-03-12 21:45 ` Patrick Maupin [this message]
2012-03-12 22:02 ` Eric S. Raymond
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='CAPz3yKeHEK3JOq3YWHSzAsQ71-U=f_0ybVgonPy39H5SW5vnFg@mail.gmail.com' \
--to=pmaupin@gmail.com \
--cc=esr@thyrsus.com \
--cc=thumbgps-devel@lists.bufferbloat.net \
/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