- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 1 Feb 2013 11:06:33 -0800
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
On Fri, Feb 1, 2013 at 6:19 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 2/1/13 1:06 AM, Tab Atkins Jr. wrote: >> You and Boris are giving me conflicting information about which is >> better. > > I don't think so. > > I just said being live is a pain to implement. Being dead, however, is a > terrible performance problem. > > I didn't state an opinion as to which is "better", or rather less bad... ;) > For this case, I think a live object is probably better. > > What I'm not convinced about is an API that has a polymorphic "immutable > string or live object" return type, because that seems like a footgun (e.g. > saving the return value and then checking it later has different behavior > depending on which flavor of the API you managed to call). > > David's proposed API does not have that problem. Yeah, I like David's API a lot. ~TJ
Received on Friday, 1 February 2013 19:07:20 UTC