Perhaps, "shipped without evidence that it actually helped". 
-
-
I baited you? How? You're using very pejorative terms, don't be surprised if you get pushback.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
But more directly, we could have done both. What frustrated me the most is that the true believers were so convinced that h2+push was the one true solution that they sidelined all parallel explorations in the same space as insta-legacy. This was wrong.
-
There has always been a fair amount of skepticism about server push in the HTTP community. Maybe we need better communication so that people don't misread intent / position of features.
End of conversation
New conversation -
-
-
The packaging group would do well to collaborate actively with developers instead of discounting their input as ideological. This would help avoid another H/2 push, and my experience on TC39 has been that engaging developers makes a huge difference in speeding up adoption.
-
Yep. Please let me know if it looks like I'm discounting any (non-crank) person's input without considering it adequately.
-
I think the main input I have not seen duly considered is on priorities. There is seemingly more interest in bundling from outside Google than the other bits.
-
I've definitely heard more interest this week in bundling than signing, but I can't ignore the 689 people who signed a letter saying the opposite either. Both will get done.
-
http://ampletter.org/ does not ask for what you’re proposing.
-
-
We should get an IETF mailing list shortly to centralize discussion. In the mean time, I'll fix
@annevk's comments on https://github.com/WICG/webpackage/pull/98 … and commit it tomorrow, after which it'll accept PRs. Is Mozilla committing to implement whatever bundling we all come up with? -
I don't personally prefer to contribute to web standards at IETF and would prefer to do this work at WHATWG, which has a community process I can easily participate in. It seems weird to ask Mozilla for an up front commitment to "whatever we come up with"
End of conversation
New conversation -
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.