You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Simon Willison@simonw·Dec 19, 2016Replying to @thomasfuchsand that example doesn't even have any CSS-in-JS in it324
Aaron Patterson@tenderlove·Dec 20, 2016Replying to @thomasfuchsi feel like you could fix this with XSLT26152
Blake Newman@blakenewman·Dec 20, 2016Challenge accepted and complete! Components with grouped concerns but still separated.712149
Brian LePore@POWRSURG·May 25, 2017Replying to @thomasfuchs and @zeldmanI personally blame Google for going overboard w/ mobile first stuff & pushing the "critical rendering path" "problem"11
zeldman@zeldman·May 25, 2017Replying to @POWRSURG and @thomasfuchsAgree tremendously with 2nd part of that statement, but don’t see “mobile first” as to blame. Mobile first + progressive enhancement FTW!11
obiefernandez.eth@obie·Dec 19, 2016Replying to @thomasfuchs and @cvJavascript is a ghetto #pffftttttt14
Patrick Lewis@Patrickml1·Dec 20, 2016Replying to @thomasfuchslooks like you forgot Aphrodite in that pic xD