Shaun Bent
Aug 9, 2017 · 2 min read

Hej, Thanks for the response. Sorry for the delay in replying to your passionate response. I really feel like I hit a nerve with you there.

To comment on a few of the points you make:

“fact that there are workarounds” — I wouldn’t describe any of the tools I’ve listed as “workarounds”, they’re all tools that have allowed me to very successfully scale CSS in large, complex projects without issue.

“ignoring them is not pragmatic” — I don’t think in anyway I have ignored these new tools. If anything I have completely acknowledge the power of these tools and what they’re trying to achieve. I merely stated that it is entirely possible to achieve the same things in our ways. What I would consider to be “not pragmatic” is to just blindly adopt a certain tool because someone says this is what we should be doing. As I have said a thousand times and will like say a thousand times more: “pick the correct tools for the problems you’re trying to solve”.

“If you feel JS community is enforcing what they think is right onto you, create your own tools in whatever programming language you want to solve them (hello sass?).” — I think you’ve missed the point of my original post with this comment. If you give my post another read you’ll see that I am saying there are tools already out there, that have been very successful for me and thousands of other developers. I don’t need to create anything.

“If you turn this into a warfare” — Interesting how the conclusion you got from my article was “warfare”, I’m not really sure anyone else has come to that conclusion.

Thank you very much for taking the time to reply, I enjoyed reading and replying to your response.

    Shaun Bent

    Written by

    Front-end Architect, currently working at @Spotify living in Stockholm, formally at @BBCSport! I own a pug! Views are my own!