- From: Brian Di Palma <offler@gmail.com>
- Date: Wed, 4 Dec 2013 21:56:58 +0000
- To: Rafael Weinstein <rafaelw@google.com>
- Cc: Dimitri Glazkov <dglazkov@chromium.org>, Anne van Kesteren <annevk@annevk.nl>, Eric Bidelman <ericbidelman@google.com>, Ryosuke Niwa <rniwa@apple.com>, Scott Miles <sjmiles@google.com>, James Graham <james@hoppipolla.co.uk>, Webapps WG <public-webapps@w3.org>
I never meant my comments to be taken as a slight toward anyone involved in the Web Components work. Neither did I mean it to be taken to mean "This work is rushed". I said, "I get the feeling that Web Components seems a specification that seems really pushed/rushed", by that I meant it seemed as if the current spec is being pushed as fast as possible toward standardization. I was not commenting on the amount of time put into making the spec but more the amount of time given to interested parties to digest, implement, and comment on it. I believe Dimitri has responded to comments to this effect by extending the time between spec transitions. I'm very excited by the possibilities that Web Components open up. I would love to see the representatives from all the implementers as excited or convinced about the spec. On Wed, Dec 4, 2013 at 7:30 PM, Rafael Weinstein <rafaelw@google.com> wrote: > On Wed, Dec 4, 2013 at 10:37 AM, Dimitri Glazkov <dglazkov@chromium.org> > wrote: >> >> On Wed, Dec 4, 2013 at 9:56 AM, Dimitri Glazkov <dglazkov@chromium.org> >> wrote: >>> >>> On Wed, Dec 4, 2013 at 4:32 AM, Anne van Kesteren <annevk@annevk.nl> >>> wrote: >>>> >>>> On Wed, Dec 4, 2013 at 9:21 AM, Brian Di Palma <offler@gmail.com> wrote: >>>> > I would say though that I get the feeling that Web Components seems a >>>> > specification that seems really pushed/rushed and I worry that might >>>> > lead to some poor design decisions whose side effects will be felt by >>>> > developers in the future. >>>> >>>> I very much share this sentiment. >>> >>> >>> It's a very reasonable and normal worry to have. I lose sleep over this >>> worry all the time. The trick that helps me is balancing it out with the >>> sadness of the geological timescale that it takes for Web platform to >>> advance. >> >> >> Just to help visualize the geological timescale, the work on Web >> Components began in late 2010 >> (http://wiki.whatwg.org/index.php?title=Component_Model_Use_Cases&oldid=5631), >> and was chartered in this WG over 2 years ago >> (http://www.w3.org/2008/webapps/wiki/CharterChanges#Additions_Agreed). >> >> To clarify my previous email: Web Components is an extremely hard problem >> with lots of constraints, and a concern would be that we miss some bits is >> totally fair. Qualifying this work as "pushed/rushed" probably ain't. > > > I'd like to make an aside about having respect for one-another's work. > > Dimitri, Alex, Dominic, Scott, Elliot and many others have put massive time > into this problem over the course of many years now, and my view is that the > design has evolved and accommodated a dizzying number of challenges and > constraints. > > "What this is attempting is big & scary" is fair. "I haven't had time to > digest the design" is fair. "I have the following specific issues" is fair. > "This work is rushed" is always understood as an indictment. > > I've seen too many talented people vote with their feet and decide life will > be less frustrating working on a closed system. Let's remember we're all on > the same team. > > AFAICT, evolving the web is fundamentally an exercise in not letting perfect > be the enemy of good. I have no doubt Web Components is imperfect, but from > what I can tell, it is *extremely* good. > > Also, go hug your mother. > > >> >> >> :DG< > >
Received on Wednesday, 4 December 2013 21:57:26 UTC