From: Dave Taht <dave.taht@gmail.com>
To: Erkki Lintunen <ebirdie@iki.fi>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] eero gains competition in plumewifi
Date: Tue, 21 Jun 2016 08:53:46 -0700 [thread overview]
Message-ID: <CAA93jw5X6Xz4uH4zqf9X=Btfn8wDYjbD9EJxoVWpkY+PQFTM-w@mail.gmail.com> (raw)
In-Reply-To: <edae8970-0c29-ca42-ac7b-4b76a571046e@iki.fi>
On Tue, Jun 21, 2016 at 1:28 AM, Erkki Lintunen <ebirdie@iki.fi> wrote:
> (resent, wrong sender address at first send)
>
> On 06/20/2016 09:16 AM, Dave Taht wrote:
>>
>> I sure wish I knew how they are implementing diversity routing and if
>> they are bothering to pay attention to make-wifi-fast
>>
>> https://www.plumewifi.com/
>
>
>
> Quite a staffing for a startup, the web site lists 46 names and positions
> from which 26 are named as engineers. Wondering if they already are in the
> business of WiFi chip and RF engineering, which enable them to do some
> "magic" to make a network of their own from the plumewifi plugs. On staffing
> resources this isn't on par with Eero, I think.
Well, it seems that post-nest there was a wave of VC investment into
making "quality" things that could be made hi-margin as market demand
(and consumer foolishness) was demonstrated to exist, by that.
Certainly wifi APs were ripe for improvements... and my own bias
towards fixing the standards and making the main APs better (e.g.
ISP-supplied or open source capable) a slower path.
The actual overheads for a company of building a shippable product
(e.g. marketing resources, manufacturing, structured testing, software
and hardware development, etc) I've long recognized, but I would have
loved to have actually had this sort of backing to go and develop a
product that worked right in the first place, long ago, and ship it.
And be making a living while doing so. I guess I'm jealous.
I really hadn't hit on the idea of the bundled, multiple AP approach
as restoring margins enough for new ideas to make it to
productization.
(I still think the all or nothing silo approach is a hard sell, even
for the classic enterprise AP vendors).
eero has published their GPL'd sources, at least, and this is the
latest of a string of products that promised way too much for what
they can possibly deliver on first ship. I keep hoping the onhub will
improve, but so far, it hasn't. And then there are so many failed
attempts with under-staffed over-promised products that have been
through kickstarter.
Ah, well, maybe this time these boxes will be be better in a
demonstrable way. Hope springs eternal.
> - Erkki
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-06-21 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 6:16 Dave Taht
2016-06-21 6:25 ` Erkki Lintunen
2020-03-30 15:44 ` Dave Taht
2016-06-21 8:28 ` Erkki Lintunen
2016-06-21 15:53 ` Dave Taht [this message]
2016-06-21 8:43 ` Maciej Soltysiak
2016-06-21 15:27 ` 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='CAA93jw5X6Xz4uH4zqf9X=Btfn8wDYjbD9EJxoVWpkY+PQFTM-w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=ebirdie@iki.fi \
/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