• It’s @D4DBoston time! (@ MIT Stata Center (Building 32)) 4sq.com/11U6Ntu

    • 0
    • 0
  • @ircmaxell where do they belong? They belong somewhere

    • 0
    • 0
  • @ircmaxell but can be discouraging to keep comments if majority of them are site related, not content related

    • 0
    • 0
  • @ircmaxell as it turns out, when I redesigned, addressed those issues, got more productive comments. They have a place

    • 0
    • 0
  • @ircmaxell off topic, yes. Spam, no. I find on blogs, comment sections tend to double as general site discussion, so still related

    • 0
    • 0
  • @ircmaxell that sounds like “censor”. Don’t like removing comments unless they are spam or truly offensive/

    • 0
    • 0
  • @ircmaxell fucking people commenting on font size instead of adding to the conversation. Almost dropped comments b/c that

    • 0
    • 0
  • My solution to @filamentgroup’s element query problem as well as CSS Viewport prefixing have been added to Toolkit

    github.com/Team-Sass/toolkit

    • 3
    • 5
  • @chriseppstein agreed. With functionality finished, we can then discuss semantics.

    • 0
    • 0
  • @chriseppstein how about @Snugug $foo :p

    • 0
    • 0
  • @chriseppstein shush you. Not entirely happy w/syntax, but can’t think of something better. Functionality > syntax

    • 0
    • 0
  • @chriseppstein what if I had a mixin called mixin? Stupid, yes, but legal

    • 0
    • 0
  • @chriseppstein oh, pfft, I’m an idiot. Maybe Sass isn’t as ingrained as we thought! Moar time here than! Still not happy w/include mixin foo

    • 0
    • 0
  • @chriseppstein if its going to be like for and each, maybe an @mixin directive instead of overloading @include?

    • 0
    • 0
  • @kenwoodworth :\ ok. We’ll hang out tomorrow

    • 0
    • 0
  • @chriseppstein …one for strings/selectors, one for var maps, one for mixins, one for functions

    • 0
    • 0
  • @chriseppstein that makes me shutter a bit. Sure you want to introduce and entirely new syntax for this? That means 4 syntaxes for interp…

    • 0
    • 0
  • @kenwoodworth yes it is. Sounds good

    • 0
    • 0
  • @kenwoodworth actually, there’s a place called beer hour by me

    • 0
    • 0
  • @kenwoodworth haha, no. Everything’s like a 10-15 min walk north of me

    • 0
    • 0
  • @filamentgroup @RWD @scottjehl :\ ok. If you guys are ever in NYC, lemme know. Also, be sure to check out @SassConf this October!

    • 0
    • 0
  • @kenwoodworth haha. That’s the other side of MIT from me (at the Hyatt), but yah, would be happy to get together for a little bit.

    • 0
    • 0
  • @kenwoodworth what’s the address at Johnny’s?

    • 0
    • 0
  • @chriseppstein @include also resembles MQ and selector interpolation. We’re really talking about int from vars as main use case, not strings

    • 0
    • 0
  • @chriseppstein so [@include](https://twitter.com/include/) mixin($foo, [arglist])? Think that’s cleaner than @include #{$foo}([arglist])? I think the later is better DX

    • 0
    • 0