@jlongster it's funny...given that focus, one imagines there would be fewer errors in your critiques. /cc @dglazkov
-
-
Replying to @slightlylate
@slightlylate@dglazkov I wouldn't say errors. You just disagree. *Lots* of other people (involved with WC) have validated my critiques.2 replies 0 retweets 0 likes -
Replying to @jlongster
@jlongster: they are (usually) category errors. You see conflict where there is none. /cc@dglazkov1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@dglazkov Web Components *really* needs better marketing, there are like 10 different uses of it being marketed right now.1 reply 0 retweets 0 likes -
Replying to @jlongster
@jlongster: how about you go first: we'll work on the marketing if you stop dropping unwarranted FUD. Deal? /cc@dglazkov2 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@dglazkov Calling this unwarranted FUD is *not* the way to address this. *Maaany* people feel like I do.1 reply 0 retweets 0 likes -
Replying to @jlongster
@jlongster : ill informed and therefore upset? A fair point. /cc@dglazkov1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@dglazkov I'm sorry you feel the need to attack without actually responding to my points.3 replies 0 retweets 0 likes -
Replying to @jlongster
@jlongster : you continue to promote myths like "WC makes you put app state in DOM". That's simply uninformed. /cc@dglazkov2 replies 0 retweets 1 like -
Replying to @slightlylate
@slightlylate@dglazkov If a menu is open or not, that is app state. WC certainly makes it hard to make it explicit.2 replies 0 retweets 0 likes
@jlongster : that's view state (and often a transient). Can keep it anywhere. WC lets components *optionally* manage some. /cc @dglazkov
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.