Chris and Dave weigh in on some of the hot drama that happened after I tweeted a joke about CSS-in-JS. Before I did that, I also hastily linked to a podcast where wrote a few quick thoughts about some of my apprehension about CSS in JS. If I had known the post would have made the rounds as much as it did, I would have crafted a more thoughtful post not on a day there was a death in my family. Note to future self.
Anyways, I appreciate how Dave and Chris got into tribalism around technologies. It was fascinating to witness multiple days’ worth of hostility from people from different camps going at each others’ throats. Somebody even flipped someone off, emoji-style.
— Rach Smith ? (@rachsmithtweets) May 8, 2018
I think being simultaneously curious and skeptical about new technologies is healthy. I hope that people try to find a balance between those worlds.
Also, thanks Dave for making the distinction between atomic design and atomic css. Atomic design has nothing to do with CSS. As I say in my book:
I show this non-web example because atomic design tends to get misinterpreted as an approach to web-specific technologies like CSS and JavaScript. Let me be clear about this: atomic design has nothing to do with web-specific subjects like CSS or JavaScript architecture. In chapter 1 we discussed the trend toward modularity in all aspects of design and development, which includes CSS and JavaScript. These are fantastic trends in CSS and JavaScript, but atomic design deals with crafting user interface design systems irrespective of the technology used to create them.