• @jacine Would you mind if I post this to the thread so it’s part of that conversation? +@thefubhy

    • 0
    • 0
  • @chriseppstein @nex3 I know, not an issue with that. It appears the issue w/my implementation is the want to have non-required vars too

    • 0
    • 0
  • @chriseppstein @nex3 Fair enough, good to know. Still trying to find a use for it.

    • 0
    • 0
  • @chriseppstein @nex3 Yes, because the max-width is defaulted to an argument higher up the stack as per common practice in these frameworks

    • 0
    • 0
  • @chriseppstein As an aside, I’m going to be in Berkeley Nov 1-5 (morning). If you’re around, would love to grab lunch/dinner/meet you.

    • 0
    • 0
  • @chriseppstein @nex3 Bad examples. First argument is a max width, second-nth are font sizes. Writing a (hopefully) smart container mixin

    • 0
    • 0
  • @nex3 @chriseppstein That’s what I’m doing. Was an attempt to find a use case for … that’s not just as simply solved with a list

    • 0
    • 0
  • @nex3 @chriseppstein Looking to let users add multiple base font sizes to a mixin input, but it’s not a required input

    • 0
    • 0
  • @nex3 @chriseppstein can I use … variable input w/an optional input? Like @mixin foo($bar: 1em, $baz: 2em…)

    • 0
    • 0
  • @ScottKellum Awesome.

    • 0
    • 0
  • @brad_frost Favorite part? It chugs on my maxed out rMBP. Who thought an almost 6MB page was a good idea? @pkattera

    • 0
    • 1
  • @ScottKellum Also going to be updated docs to be more user friendly, can those go straight in?

    • 0
    • 0
  • @ScottKellum I’ve got Container written + ability to have multiple containers along same lines as Grids. Can I commit straight to master?

    • 0
    • 0
  • RT @brad_frost: Blame the implementation, not the technique timkadlec.com/2012/10/blame-the-implementation-not-the-technique Ridiculously good article by @tkadlec. Ridiculously.

    • 0
    • 0
  • @webchick I can’t tell if TB is for Component Library, which belongs in Contrib, or Markup, which we’re doing in Twig. @rupl @lewisnyman

    • 0
    • 0
  • @webchick One of the issues is FE is working on what FE is concerned with, fixing the theme layer and actual output. @rupl @lewisnyman

    • 0
    • 0
  • @webchick Agreed we need to attract more FE, but “anything’s better than nothing” isn’t good enough, and TB is crap. @rupl @lewisnyman

    • 0
    • 0
  • @mylittletony they are and it’s frustrating. Don’t know what to do about it.

    • 0
    • 0
  • @webchick, I couldn’t agree with @rupl @lewisnyman more.

    • 0
    • 0
  • After further consideration, I’ve decided that #HIMYM needs to be an hour long show, not a 30 min show. Ends too soon.

    • 0
    • 0
  • @mortendk @krisbulman We may. I await your post.

    • 0
    • 0
  • I feel as if this was my day: xkcd.com/386

    • 0
    • 0
  • @mikeefreedom @boztek …that are adaptable to any design, not just the generalization of a framework.

    • 0
    • 0
  • @mikeefreedom @boztek using a CSS Preprocessor, especially Sass, it becomes trivial to create design tools instead of prebuilt frameworks…

    • 0
    • 0
  • @krisbulman @mortendk I think the issue is the thought that TB will help foster a front end community; it will not.

    • 0
    • 0