Blaze CSS – Open Source Modular CSS Framework

  • "Un-opinionated" right next to "BEM". It's like saying WinAPI and COM is un-opinionated.

  • Really nice. The only thing that would prevent me to give it a real go to is that it is a one man project not backed by any company...

  • This looks really good. The grid is much more customisable than bootstrap/foundation.

  • Is there a reason beyond the marginal performance difference, why there are no global modifiers in BEM?

    I find the c-button c-button--primary a bit annoying. Why not just c-button primary and define them like this?

        .c-button.primary {
          …
        }
    
    
    Or namespace it:

        .c-button.m-primary {
          …
        }

  • Small thing I noticed: on http://blazecss.com/components/buttons/, the 'link' button made from a normal <a> tag is slightly larger (Chrome 51).

  • Quite nice.maybe will be used it for future replacing twitter bootstrap.

  • I love the opt-in part. I really like building stuff in Bootstrap but I loathe the fact that it changes a lot of stuff implicitly, making me feel I lose control.

  • Despite "un-opinionated" being one of their main selling points, using BEM is SUPER opinionated.

  • Your dashboard example is freaking out a little.

    Here is a short clip of it: https://www.freeih.com/tAgTSr

  • Typo on the front page, 2nd info box - "Mirco-frameworks tend to sacrifice a lot of usefulness for the file size, leaving the developer wanting more".

  • Resizing feels very snappy!