The Cost of the “S” in HTTPS https://www.cs.cmu.edu/~dnaylor/CostOfTheS.pdf …
-
-
Replying to @JoeBeOne
@JoeBeOne@ivanristic : the methodological issues with this paper make my skin crawl. PhantomJS doesn't support SPDY, AFAICT /cc@igrigorik2 replies 2 retweets 6 likes -
Replying to @slightlylate
@slightlylate@JoeBeOne@ivanristic no TLS False Start (1RTT handshake), no SPDY (multiplexing)... please redo with a real browser!1 reply 1 retweet 2 likes -
Replying to @igrigorik
@igrigorik: I think this is another argument for Headless Blink /cc@JoeBeOne@ivanristic@wycats3 replies 0 retweets 5 likes -
Replying to @slightlylate
@slightlylate@igrigorik@JoeBeOne@ivanristic@wycats I dunno. Can't we just spend time fixing some of Chrome's many broken things first?3 replies 0 retweets 1 like -
Replying to @sleevi_
@sleevi_ Imagine if you couldn't write reliable, automatic tests in blink. That's state of web platform.@slightlylate@igrigorik@wycats2 replies 0 retweets 2 likes -
Replying to @frgx
@frgx So we just gave up on WebDriver and friends then? Plenty of tools already exist in this space...@slightlylate@igrigorik@wycats3 replies 0 retweets 0 likes -
Replying to @sleevi_
@sleevi_ That's the disconnect: used to think so but try using WebDriver or writing tests for this stuff.@slightlylate@igrigorik@wycats1 reply 0 retweets 0 likes -
Replying to @frgx
@frgx Having reliable CI catching bugs in a 6-week framework release cycle means headless REAL browsers.@sleevi_@slightlylate@igrigorik2 replies 5 retweets 4 likes -
Replying to @wycats
@wycats exactly. For example, the Vine CSP Chrome crash could have been caught earlier :(@sleevi_@slightlylate@igrigorik2 replies 0 retweets 0 likes
@frgx Ember bugs that can be caught in PhantomJS are fixed orders of magnitude faster @sleevi_ @slightlylate @igrigorik
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.