-
-
Replying to @matthewcp
@matthewcp@wycats Not for most things. How do you explain HTML tags? Or CSS layout? Could you implement your own in JS?1 reply 0 retweets 0 likes -
Replying to @matthewcp
@matthewcp what the manifesto calls for is pointer events JS library by browser vendors (a la Polymer)@domenic1 reply 0 retweets 0 likes -
Replying to @matthewcp
@wycats@domenic my concern is this manifesto only benefiting library/platform devs. Someone suggested <audio> implemented in JS.2 replies 0 retweets 1 like -
Replying to @matthewcp
@matthewcp I want <audio> to be iterable in JS. I don't want most web developers to be implementing their own <audio>.@domenic2 replies 0 retweets 0 likes -
Replying to @matthewcp
@matthewcp <audio> was hardly useful from day 1. Manifesto recommends browser vendors build <audio> when they ship Audio API.@domenic2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@matthewcp right, it's not either high-level or low-. It's that high level shouldn't be explained as "then some C++ magic happens!"2 replies 0 retweets 0 likes
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.