Just to be clear, those are NOT the issues that led me to give up on the webperf working group. The fundamental approach to specs did.
-
-
Replying to @really_bz @bz_moz and
we've been chipping away at the plan we defined in: https://lists.w3.org/Archives/Public/public-web-perf/2015Jun/thread.html#msg96 …, 10k-foot view: https://docs.google.com/document/d/1ZKW9N0cteHgK91SyYQONFuy2ZW6J4Oak398niTo232E/edit …
2 replies 0 retweets 0 likes -
Replying to @igrigorik @bz_moz and
and we're (really) close to finally having that all aligned, I think. next up is focusing on integrations? curios to hear your priorities.
1 reply 0 retweets 0 likes -
Replying to @igrigorik @annevk and
My priority is to be able to read a definition of an interface or interface member in a spec and be able to implement it.
1 reply 0 retweets 1 like -
Replying to @really_bz @igrigorik and
Without having to magically know about other specs that monkeypatch its behavior in weird ways.
1 reply 0 retweets 1 like -
Replying to @really_bz @igrigorik and
There is no way people can keep all of the web platform in their heads at once; we should be writing specs so they don't have to.
1 reply 0 retweets 2 likes -
Replying to @really_bz @igrigorik and
Now in terms of techniques, that means no action at a distance, explicit links to relevant other things, no COMEFROM specs.
1 reply 0 retweets 0 likes -
Replying to @really_bz @igrigorik and
And by "explicit links" I don't mean "in an appendix".
1 reply 0 retweets 0 likes -
Replying to @really_bz @igrigorik and
I mean just reading through the localized spec bit and following links from it should reach all the information needed to implement.
2 replies 0 retweets 0 likes -
Replying to @really_bz @bz_moz and
this all sounds reasonable, and as far as I can tell, aligned with what we've been working towards. Followed up on the webperf thread.
1 reply 0 retweets 0 likes
Yes, that's what I've been hearing for years, and no progress has happened. If it happens this time, great, but without me. I'm done.
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.