Joshua, 

 

You are absolutely correct.  "higher-order bit" it is.  Even better.  Can
you imagine what a former English major's imagination did with that?  

 

n

 

From: Friam [mailto:friam-boun...@redfish.com] On Behalf Of Joshua Thorp
Sent: Sunday, March 24, 2013 3:01 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: Re: [FRIAM] Just sent this to the Google Device Support Team

 

Also I doubt Owen ever said "top bit",  I imagine it was probably
"high-order bit".

 

I like the question though, can a bug be on purpose.  Seems like it would be
in the eye of the beholder, one person's bug might be another's feature.

 

--joshua

 

On Mar 24, 2013, at 2:57 PM, Douglas Roberts <d...@parrot-farm.net> wrote:





Nick's counselling session will be scheduled shortly...

 

--Doug (Who can tell when his chain is being yanked.)

 

On Sun, Mar 24, 2013 at 2:53 PM, Nicholas Thompson
<nickthomp...@earthlink.net> wrote:

Now you all know, that, ever since Owen first used the word "top bit" in my
presence, nearly a decade ago, I have followed, with rapt attention, the use
of language on this list.  So,  you guys.  I need to understand this better.
Can a "bug" be "on purpose"?  It sounds to me like Google has sabotaged its
own product, right.  Therefore, if I understand the language, any Nexus
phone thatactually  worked, would be "buggy"., by definition.  I am sorry to
bother you about this, but these are the kinds of things that keep me awake
at night.  N

 

From: Friam [mailto:friam-boun...@redfish.com] On Behalf Of Douglas Roberts
Sent: Sunday, March 24, 2013 1:44 PM
To: The Friday Morning Applied Complexity Coffee Group
Subject: [FRIAM] Just sent this to the Google Device Support Team

 

Hi, Google Device Support Team.

 

It's  been a while since we spoke, but I recently discovered that someone in
your organization has been (I hope inadvertently) disseminating inaccurate
information about this Nexus 4
<https://productforums.google.com/forum/#!msg/mobile/l4uYRMVHnHY/rHpsXdwNGPc
J>  bug, and I thought you'd want to know about it right away.  

 

Here's the deal: you see, we all know that the Nexus 4 was not designed on
purpose to prevent wifi and bluetooth from being used at the same time.  We
all know that it is a bug.  Well, all of us except for Steve, apparently.
Here, read for yourselves:  

 

http://things-linux.blogspot.com/2013/03/translated.html

 

Now, we all have the utmost confidence that someone in your organization
will immediately take Steve aside for a private little counselling session
about the inappropriateness of, shall we say, bending the truth regarding
this particular flaw in the Nexus 4 product.

 

Thanks for your prompt attention to this matter.

 

Best,

 

--Doug

 

-- 

Doug Roberts
d...@parrot-farm.net

 <http://parrot-farm.net/Second-Cousins>
http://parrot-farm.net/Second-Cousins


505-455-7333 - Office
505-672-8213 - Mobile


============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com





 

-- 

Doug Roberts
d...@parrot-farm.net

 <http://parrot-farm.net/Second-Cousins>
http://parrot-farm.net/Second-Cousins


505-455-7333 - Office
505-672-8213 - Mobile

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

 

============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com

Reply via email to