Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)

Peter Thatcher <pthatcher@google.com> Fri, 19 July 2013 17:38 UTC

Return-Path: <pthatcher@google.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB6B21E80DF for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 10:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.734
X-Spam-Level:
X-Spam-Status: No, score=-1.734 tagged_above=-999 required=5 tests=[AWL=0.243, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxzGfzuNb5lD for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 10:38:22 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 9877E21E805D for <rtcweb@ietf.org>; Fri, 19 Jul 2013 10:38:12 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id rl6so4719354pac.1 for <rtcweb@ietf.org>; Fri, 19 Jul 2013 10:38:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wbYZ8f+09h3ZTVUD2N60rza86G5gd/7k0R3xkBD/x6c=; b=As5Lk09HQc5BYusiLDhonuUtcUUcyunSYNlwGzTxyk7tjHJppobxlMMbDPi9qsOAFu 5zDP86+ppQbVyLk55QfQKOUAFfsFKU7ClzE+4i5+IvyExNMC8SDYb00YfQT8PxU32wWe qkF5Omj9s6AR7oZKnrGOqQSt0W1oSmcp3XzyF1tFHIOo3ATyUy7NST6QRW2N+/kCXtBg 0xl352o8EgkgeiiGy9u/8vo0HxzXE66ssLtXhCOH5mWdhjg8YusPO81POeBRdT6Kh9XU RWbejJSwBStb7pBh9qayxSdpiNbSxSfUwBRgMx1I3S6lXJkveyH9SC0uJGsuPuxxoYmm zNPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=wbYZ8f+09h3ZTVUD2N60rza86G5gd/7k0R3xkBD/x6c=; b=CIIe1bP7YOJly6Eeuq2C2hgisfiVRDhQN4ad6BYw5YqMSIkC1ISRLBWtRLf595pquR F4aXEsCDyQX9Jz13SJIGXezNlCvVa5JPctwrKdrINxKRmi5Y1BZDz17ymDNNI4XlIZwd 2rjp6GbwZnf29SHBHKpaun6K11bF4ewpp9lUyG/22OG6lE9iOxs/KzK5lN0iT+dKZjmk 8F+/iYwJh5yd9BUNqnr908KvbjgkTQWwvRK2s0P7UOGIuFzfkG/szbW+ujWYTAjSyZUE PuOMSw7JM3Zk8GMtXZkTvDXvIzEhfQRwfIxjVfuI0DAsmPU/0Jp2wHA8DUXARiRXTQSV 0TRQ==
X-Received: by 10.66.4.6 with SMTP id g6mr9424791pag.96.1374255492272; Fri, 19 Jul 2013 10:38:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.78.195 with HTTP; Fri, 19 Jul 2013 10:37:31 -0700 (PDT)
In-Reply-To: <51E977DB.5010002@nostrum.com>
References: <CAJrXDUGMohpBdi-ft-o_uE7ewFkw7wRY9x7gYEncjov7qi-Bew@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30BC0F@ESESSMB209.ericsson.se> <CAD5OKxtKLMf_d=8GSMrqfNhDHPe9MFP2ZTKzZHFn9CyMr-gSVQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30C833@ESESSMB209.ericsson.se> <CAD5OKxvGfkgRp6tXwbOu_kVteHiBBqsyR5ixH18FMKjCNGO8VQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30CD1E@ESESSMB209.ericsson.se> <BLU401-EAS386F88B3FE140492B39B59693610@phx.gbl> <AE1A6B5FD507DC4FB3C5166F3A05A484213E41E7@TK5EX14MBXC265.redmond.corp.microsoft.com> <C50FDAD5-492C-4A83-AD6D-464242FB4A05@iii.ca> <CALiegfneUj=kzDjR_E1=S-bqAajaPUE3f_A2g8oGriFyPhamPA@mail.gmail.com> <51E96B5B.2050302@nostrum.com> <CABkgnnXa-eTzRHcLMnHam4c+1D9kkvRwi9=V-9P43+p+pKE_sw@mail.gmail.com> <CA+9kkMCjt2UHFynLqwns0J0f5ZtnxtMX3ppzR66e5q_rJ9D5Ug@mail.gmail.com> <51E97677.1020902@nostrum.com> <CAJrXDUGLwOEWCbZU8vS53pW9fZt_RdeKgmmw9My-dbgDn_PkqQ@mail.gmail.com> <51E977DB.5010002@nostrum.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 19 Jul 2013 10:37:31 -0700
Message-ID: <CAJrXDUFc7JGr+uESKRd2+GB=HQfoyzwAeH+fL0Upa3cEVbmf2Q@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="bcaec520e9f772be3404e1e0ca00"
X-Gm-Message-State: ALoCoQnqk91ux5BQ5gp9KqWh1sa1LbhCsQN6TCaLUiUyLN4tAOrC3qnBEpOUH6WTqlpLGI2+cWIhJo9azsVhs9oFW19ZEZffcYp/GYrEzwVCfXXtIGalmA1jYrxLMl1ukyOXg+S/q8uHljcXzTNCto4Skv/CeEODADpwSP+yEkVJSZM9pwougFVSYept0l0R4PUMJk6g+SmF
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 17:38:22 -0000

On Fri, Jul 19, 2013 at 10:31 AM, Adam Roach <adam@nostrum.com> wrote:

>  On 7/19/13 12:27, Peter Thatcher wrote:
>
>
>   But, honestly, any course of action that relegates this to the
>> applications seems to have the dual properties of forcing it to be
>> implemented hundreds of thousands of times while making the actual user
>> experience worse.
>>
>
>  Hundreds of thousands of times?
>
>
>
> How many web apps do you anticipate will use real time communications
> between now and the time that this work becomes obsolete?
>

That's an excellent point.  Along with that, how many will only be using
the data channel?  And how many will be using something other than SDP for
signalling?  And how many will be doing lots of SDP munging?  And how many
libraries will be written to hide the ugliness of SDP?  Hundreds of
thousands?


>
> It's not important to come to consensus on this number -- my key point
> here is that it's significantly more than the number of web browsers that
> will be developed in that time, and by several orders of magnitude.
>

That's an excellent point.  If we spent a little bit of extra work making a
really good API, think of how many people will benefit.  It's several
orders of magnitude more than the number of web browser that will need to
do a little bit of extra work to implement a good API.


>
>
> /a
>