Shifting responsibility to browsers can let them fix shitty websites, but it can also be a bottleneck for progress on good websites.
-
-
Replying to @sebmarkbage
I empathize strongly w/ browser vendors trying to solve the under-maintained web. I also empathize w/ devs/publishers feeling held back.
1 reply 1 retweet 7 likes -
Replying to @sebmarkbage
@sebmarkbage are you referring to the likes of AMP?1 reply 0 retweets 0 likes -
Replying to @joecritch
@joecritchley Nothing in particular. Just saying there's an inherent conflict between publishers being in control (JS libs) or the browser.2 replies 0 retweets 0 likes -
Replying to @sebmarkbage
@joecritchley Browsers like to think of themselves as the friendly third-party that makes it better for both publisher/consumer. Not always.1 reply 0 retweets 1 like -
Replying to @sebmarkbage
@sebmarkbage@joecritchley An example of this is a push towards no-eval CSP, which disallows lazy-evaluation in frameworks.1 reply 0 retweets 2 likes -
Replying to @wycats
@wycats@sebmarkbage Security wise csp's are great! Aren't there other ways to do lazy?2 replies 0 retweets 0 likes -
@JJoos @sebmarkbage "lazy" by definition means "eval". They are describing the same exact thing.
-
-
Replying to @wycats
@wycats@sebmarkbage ah sorry missed the context, was thinking about lazy as in lists...0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.