• @lewisnyman haha really? That’s awesome! I love Microsoft, I do.

    • 0
    • 0
  • @lewisnyman not surprised no touch; their current mobile offering doesn’t actually support Touch

    • 0
    • 0
  • Siri is a lying no good so-and-so. I specifically asked her if it was going to rain today, and she smugly told me no.

    It’s raining.

    • 0
    • 0
  • RT @wilto: “At Adobe, we’ve realized that you want simple, no-BS tools. So we’re proud to announce Creative EdgeCloud Pro 2012 MX where …

    • 0
    • 0
  • @AlexGaringer @aaron_lax Haha! Indeed they are!

    • 0
    • 0
  • @AlexGaringer Hey Cuz!

    • 0
    • 0
  • @justin_devon Build Mobile First and write a no query static stylesheet. 90% this is just for IE, so if needed, load w/IE conditional.

    • 0
    • 0
  • @justin_devon To paraphrase “If you’re trying to make IE responsive, stop and say that out loud”

    • 0
    • 0
  • Instead of a bunch of small Sass BoFs at @BADCamp, I’ve proposed a mini training! Go vote for it now!

    2012.badcamp.net/program/sessions/mini-training-responsive-web-design-sasscompass

    • 1
    • 0
  • @geoffhasson I would, but don’t want to be /that/ guy. Just know its a training company in NYC

    • 0
    • 0
  • Presenter, repeats after me. There is no such thing as “mobile content”.

    • 0
    • 0
  • No! No no no no no! You do NOT use Facebook’s switch to native as a web/native performance example! Read the whole damn interview! #rwd

    • 0
    • 0
  • Also, he’s missed the point of Progressive Enhancement. You don’t have the default be the feature and enhance if it doesn’t exist!

    • 0
    • 0
  • Wow. Presenter’s live, professional site is using a full, unoptimized Modernizr build. WTF?

    • 0
    • 0
  • You can’t talk about progressive enhancing to <canvas> without talking about accessibility concerns. You need both! #a11y #rwd

    • 0
    • 0
  • @chriseppstein :p indeed it would be!

    • 0
    • 0
  • (Sorry all. Wasn’t planning on live tweeting this meetup)

    • 0
    • 0
  • Note to presenter: lots and lots of people are talking about not hiding content for small screens. Open your ears! #rwd

    • 1
    • 1
  • Respond.js should /never/ be your go-to solution. It’s bad JS and bad practice. No query stylesheets much better practice. #rwd

    • 1
    • 1
  • Room full of #rwd noobies and it’s “mobile, tablet, desktop” complete with device based PX media queries. I wanna correct, but its rude. Bah

    • 1
    • 0
  • When showing responsive video, don’t go for the JS solution over intrinsic ratios! Ratios are the wow factor, and the better solution! #rwd

    • 1
    • 0
  • Mobile First isn’t “an initiative” in #rwd, it’s the best practice.

    • 2
    • 1
  • @chriseppstein also, a difference between choosing to do desktop first when you understand mobile first, another to teach as default.

    • 0
    • 0
  • @chriseppstein oh darling, can I point you to @codingdesigner and my Breakpoint @Compass extension? It’ll make u happy

    github.com/canarymason/breakpoint

    • 0
    • 0
  • Also, it pains me that people are still teaching device breakpoints and desktop first for #rwd.

    • 1
    • 0