@divya My point is we should stop doing that and not ship things on the open web until they're more stable. And make them stable sooner.
-
-
Replying to @really_bz
@bz_moz@divya specification process is not just asking implementers, but doing what authors need. So let them use it early but prefixed.1 reply 0 retweets 0 likes -
Replying to @dirkschulze
@dirkschulze@divya Do you think shipping preffed off is not enough to get decent author feedback?1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@divya I guess not. I fear authors won't use features if they are not activated. Therefore no feedback from the target audience.1 reply 0 retweets 0 likes -
Replying to @dirkschulze
@dirkschulze@divya It really depends on whether you want use in experiments or production sites.... and we _don't_ want use on the latter.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@divya Once you create serious content, you recognize specification and implementation issues. Sth. that we need before RC state.1 reply 0 retweets 0 likes -
Replying to @dirkschulze
@dirkschulze@divya We should be unprefixing before RC. Imo, once you have serious content, if you haven't unprefixed yet you screwed up.1 reply 0 retweets 0 likes -
Replying to @really_bz1 reply 0 retweets 0 likes
-
Replying to @dirkschulze
@dirkschulze You're quite limited way before that, because authors are taught to include the unprefixed decl with the prefixed ones.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz That would be an argument not to use prefixes from the beginning.1 reply 0 retweets 0 likes
@dirkschulze Yes, indeed. Pretty much what @hsivonen has been saying for a while now.
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.