Tired of explaining to working groups that hidden action at a distance makes it hard to read and implement specs. They just don't care.
-
-
Replying to @really_bz
So I have decided to stop caring too, because my sanity is more important to me at this point that covering up other people's mistakes.
1 reply 1 retweet 3 likes -
Replying to @really_bz
Web Performance Working Group, I'm looking at you specifically.
2 replies 0 retweets 2 likes -
Replying to @really_bz @bz_moz
Feel free to ping me anywhere with a bit of context and I'll follow up for you. Filed https://github.com/w3c/navigation-timing/issues/63 … on them today.
2 replies 0 retweets 0 likes -
I wish
@igrigorik would make it a bit more of a priority. There’s similar issues with undefined caches for rel=preload and friends.1 reply 0 retweets 1 like -
Replying to @annevk
the undefined caches go beyond preload. Agree they need to be defined. On my (admittedly crowded) TODO list /
@bz_moz@igrigorik1 reply 0 retweets 1 like -
Anne: believe me, it's not for the lack of interest.. there's only so many hours in a day.
1 reply 0 retweets 2 likes -
I think the balance between increasing and reducing technical debt has been off.
2 replies 0 retweets 1 like -
my main focus across our L2's has been to rationalize/unify concepts and layering across the previous (L1) specs /cc
@toddreifsteck2 replies 0 retweets 0 likes
The trouble is, the L1 spec setup was already broken. And L2 piled more brokenness on top of it, making it even harder to make sense of it.
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.