@patrickhamann couldn’t agree more.

RT @codepo8: If you think that the average web site being 2MB isn’t an issue, exhibit A. 12GBP for 10MB roaming. @EE you’re drunk. http://t…

@AlwaysWorking yup, that’s my plan

@AlwaysWorking it was chrome

@AlwaysWorking haha

Why #perfmatters, even on “desktop”. Took me an 1.5 hours (mostly loading) and 80% of my laptop battery to make 3 simple travel bookings

RT @ryan_brownhill: I just published “Crafting Easing Curves for User Interfaces” medium.com/@ryan_brownhill/crafting-easing-curves-for-user-interfaces-34f39e1b4a43?source=tw-47efdcca644d-1431199054362

I have also apologized directly to the speakers. I am sorry my actions detracted from their much-needed discussion on the complexity of FED.

My actions yesterday were wrong, not reflective of the community I love, and I must do better. I’m sorry

@sara_ann_marie We good. I’m likewise sorry if my comments were taken personally by you, was not meant to be directed at you personally.

@lyzadanger It seems as if I misspelled your Twitter handle. I would like to apologize for yesterday… Snugug/596385497762631680

@sara_ann_marie …and I thank you for keeping a cooler head yesterday than I did.

@sara_ann_marie I understand and appreciate that. I’m sorry for the unproductive tone my comments took yesterday…

@susanjrobertson :\ Again I’m truly sorry that I made you feel that way.

@rachelandrew @llyzadanger @jefflembeck @susanjrobertson …were having was a good one and I did not mean to take away from that.

@rachelandrew @llyzadanger @jefflembeck @susanjrobertson …was marketed. I am truly sorry that it came off that way. The conversation you…

@rachelandrew @llyzadanger @jefflembeck @susanjrobertson …It was not meant to be directed at you four, but rather at how the event…

@rachelandrew @llyzadanger @jefflembeck @susanjrobertson I would like to sincerely apologize about my Tweet storm yesterday…

@wilto @sophshepherd I’m sorry it came across that way. It was not directed at the speakers, but rather how ALA marketed/promoted the event.

Rather, it rather directed at @alistapart and how the event was marketed/promoted, giving the impression it would be about @SassCSS (2/2)

In case it wasn’t clear, yesterday’s thread on #SassTalk was not directed at the speakers. Their conversation was great and engaging. (1/2)

Just voted for the sessions I want to see at @CSSDevConf, and you should too! Trends I saw? Flexbox and Style Guides

ow.ly/MzMNl

BTW we release Gulp Sass 2.0 today that fixes a bunch of stuff and brings you Node Sass 3.0 and LibSass 3.2 github.com/dlmanning/gulp-sass

RT @xzyfer: @chriseppstein the misinformation and FUD around LibSass bums me out. I don’t think we can make it any easier to get accurate i…

@dandineen NP @sassxsw @mbarker_84