That’s a relief. Your comment made me worry that the whole idea was stalled
-
-
They've been talking abt async-append "coming first" since June 2016 when I posted. Reduced enthusiasm in other vendors I was talking to.
1 reply 0 retweets 0 likes -
"doesn't have good prospects in standards" afaict means
@slightlylate and colleagues at chrome are negative internally. Frustrating.1 reply 0 retweets 0 likes -
I'm very very interested in working through whatever concerns people have. But so much time is going by with little progress.
1 reply 0 retweets 3 likes -
Hear you loud and clear.
1 reply 0 retweets 3 likes -
Thanks. I'm here whenever :)
1 reply 0 retweets 0 likes -
@wycats, what’s your take on async append? Would that satisfy your needs?1 reply 0 retweets 0 likes -
No, for reasons I talked about in both the DOMChangeList proposal and on an async-append repo. I don't object to async-append ...
1 reply 0 retweets 0 likes -
but don't see why it has to block work on the DCL primitive, especially given the lack of details around the ostensible proposal.
1 reply 0 retweets 0 likes -
1: To be specific: DCL allows cross thread construction, coalesces changes and avoids unneeded allocations.
1 reply 0 retweets 0 likes
2/2: It's also a good fit, as is, for today's wasm. No objections to other primitives, but want those features.
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.