↵

MaintainableCSS - an approach to writing modular, scalable and of course, maintainable CSS(maintainablecss.com)

over 7 years ago from Adam Silver, Interaction designer focused on inclusive design and design systems

  • Thomas Michael SemmlerThomas Michael Semmler, over 7 years ago

    Could you please elaborate on how this differs from BEM?

    0 points
    • Dominik PoradaDominik Porada, over 7 years ago

      Looks like written by someone who doesn’t like the syntax of BEM.

      1 point
    • Adam Silver, over 7 years ago

      Your comment is a fair one so thank you for that. There are similarities to BEM. There are also similarities to ecss.io so go check that one out too.

      A few small notes: The terminology is different - I think this is more readable (but then I would, wouldn't I? :)...and for me readability is very important (something I talk about early on in MaintainableCSS)...the rationale behind it comes from a different viewpoint (mine) and there are more chapters to come all of which I think are beneficial.

      For the benefit of the comment below...there are many methodologies "out there" of which many are similar but I don't think that is reason enough to not to share the approach. Myself and other people I have worked with for many years have found value in it, so getting this out of my head and sharing it with the community feels like a positive thing to do.

      1 point
      • Thomas Michael SemmlerThomas Michael Semmler, over 7 years ago

        The Terminology is different, yes - and its fair enough that you basically just shared your modified BEM-Approach, which is basically an iteration of smacss, which is basically an iteration of oocss (As far as I see it). But besides the terminology and the fact that you use single dashes to separate the .module-component-state { }, there is no actual difference. But I personally think there doesn't have to be a major difference. It works for you, thats great. I personally would deem this kind of code highly unreadable, but I am very used to writing BEM - so I guess thats only natural then :P

        For the benefit of the comment below...there are many methodologies "out there" of which many are similar but I don't think that is reason enough to not to share the approach

        And you should also never stop sharing, no matter how salty any comment gets. Not because other people profit from it, but because it demonstrates acting based on values.

        But also understand, that people criticize things heavily nowadays based on the fact that more and more people share recycled and useless things in the content bubble we are in, in order to get exposure, which will translate into money, eventually. Such people are basically exploiting the humans who work in this industry. That is in a way of course no different from countless prototyping tools who all just try to get our money, despite how noble their goal to solve that one problem that nobody truly has: animation in wireframes and mockups might be marketed.

        btw, thanks for sharing ecss.io - I had not heard of it before!

        0 points