Re: [hybi] Anti-patterns (was Re: I-D Action:draft-ietf-hybi-thewebsocketprotocol-01.txt)

"Shelby Moore" <shelby@coolpage.com> Fri, 03 September 2010 02:06 UTC

Return-Path: <shelby@coolpage.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61B8A3A67B1 for <hybi@core3.amsl.com>; Thu, 2 Sep 2010 19:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.335
X-Spam-Level:
X-Spam-Status: No, score=-2.335 tagged_above=-999 required=5 tests=[AWL=0.264, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UuLCQbKdpMjk for <hybi@core3.amsl.com>; Thu, 2 Sep 2010 19:06:48 -0700 (PDT)
Received: from www3.webmail.pair.com (www3.webmail.pair.com [66.39.3.34]) by core3.amsl.com (Postfix) with SMTP id C347C3A6403 for <hybi@ietf.org>; Thu, 2 Sep 2010 19:06:47 -0700 (PDT)
Received: (qmail 7542 invoked by uid 65534); 3 Sep 2010 02:07:16 -0000
Received: from 121.97.54.174 ([121.97.54.174]) (SquirrelMail authenticated user shelby@coolpage.com) by sm.webmail.pair.com with HTTP; Thu, 2 Sep 2010 22:07:16 -0400
Message-ID: <d090cb995c72349eefb2caa342e721a6.squirrel@sm.webmail.pair.com>
In-Reply-To: <e4d27f72fc2f748051b28d5b35c98d4a.squirrel@sm.webmail.pair.com>
References: <e0b4f16de694ec610c00bd55b1dd7ad1.squirrel@sm.webmail.pair.com> <3ECFC088-CAE9-4082-8B62-EBED891AC767@gbiv.com> <e4d27f72fc2f748051b28d5b35c98d4a.squirrel@sm.webmail.pair.com>
Date: Thu, 02 Sep 2010 22:07:16 -0400
From: Shelby Moore <shelby@coolpage.com>
To: shelby@coolpage.com
User-Agent: SquirrelMail/1.4.20
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Hybi HTTP <hybi@ietf.org>
Subject: Re: [hybi] Anti-patterns (was Re: I-D Action:draft-ietf-hybi-thewebsocketprotocol-01.txt)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: shelby@coolpage.com
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2010 02:06:52 -0000

The _ONLY_ positive scaling paradigm on the internet is the Bazaar...



[snip]

>> Natural systems self-organize.  Software systems do not.
>
>
> First it is not correct to imply that running software can not
> self-organize without programming

[snip]

> I suggest to you that is has already been proven that lowering the cycle
> costs for the feedback synergy loop between what software is doing and the
> programming (i.e. Bazaar and peer programmer model) squashes the Cathedral
> model in the reality of the free market:
>
> http://www.catb.org/~esr/writings/cathedral-bazaar/
>
> And WebSockets is about applications, application programmers, and end
> users. That is an evolutionary feedback system.


The _ONLY_ positive scaling paradigm on the internet is the Bazaar!

Listen to this, especially around the 4:20:

http://www.catb.org/~esr/writings/cathedral-bazaar/linux1_d50_48kbs.mp3
(48kbps)
http://www.catb.org/~esr/writings/cathedral-bazaar/linux1_d50_96kbs.mp3
(96kbps)



[snip]

> well as P2P.  However, the basic presumption of the WWW is that user is
> the programmer.  HTML was specifically designed for the amatuer
> programmer. And WebSockets opens a whole new world of possibilities
> especially if we don't force users to interact with a server. Rather
> spontaneously users could start interacting with each other.

Listen to the first 1.5 mins of the above audio, where it is explained
that half-amateur programmers bashing on code and releasing new
executables every day, evolves 6 months faster than cathedral models of
software evolution.

Heck as further evidence, we can't even produce a simple orthogonal
fragmentation framing and semantic message layer[7] in this WG without
getting bogged down in so many conflated issues (authentication,
cross-protocol security, encryption, etc) that have nothing to do with
WebSocket. First draft WebSocket, and leave those other things for the
market or a new WG to handle orthogonally. Don't conflate everything and
paralyze your evolution.  Smallest atomic things are the fastest.


[7] http://www.ietf.org/mail-archive/web/hybi/current/msg03901.html
http://www.ietf.org/mail-archive/web/hybi/current/msg03919.html
http://www.ietf.org/mail-archive/web/hybi/current/msg03854.html
http://www.ietf.org/mail-archive/web/hybi/current/msg03833.html