CSS is incredibly flexible permalink
Imagine if a tech dude walked on stage at a conference and said the following:
“This declarative language will gracefully continue on failure, allow you to write global and scoped code, and it will work across your entire front-end stack, wether it’s rendered by a framework, a CMS or a static HTML file”
People would lose their damn minds and Hacker News would probably melt down. Now, if I make a slight amendment to that, the reception would probably be the exact opposite.
“CSS will gracefully continue on failure, allow you to write global and scoped code, and it will work across your entire front-end stack, wether it’s rendered by a framework, a CMS or a static HTML file”
My favourite feature of CSS is this incredible flexibility. We can use CSS to style web pages, style complex apps, produce art, create stunning animation and even layout a printed asset. This portability makes CSS knowledge a super transferable skill to have, so next time someone on Twitter says otherwise, think back to this section instead.
There are fantastic methodologies for component driven CSS permalink
A popular “critique” of CSS is that “you can’t build components that scale efficiently”. This, my friends, is utter poppycock. Thanks to methodologies such as BEM and SMACSS, there’s a plethora of solid, tested options for doing exactly that. You can even import these CSS components into your React components if you want.
So, again, if someone says “you can’t build components that scale efficiently”, you now know that they are very likely talking out of their arse.
Some brilliant people who evangelise and work hard on CSS permalink
Did you know that there’s an official working group for CSS? The CSSWG meet regularly and discuss new features of the language to create specifications for browser vendors to implement. Take a moment to look at the mind-blowing talent that make up the CSSWG’s members list. Thanks to these fabulous people, newer features such as CSS Grid landed with huge levels of support very quickly. At the time of writing CSS Grid has 88.17% global support. This is great for a feature that landed less than 2 years ago!
I’d also like to link you up to some of my favourite CSS people’s Twitter profiles. I’d recommend that you follow them to give your feed some balance in preparation for when we get into one of our frequent arguments. Here’s a rather exhaustive list to get you started:
Let’s hope that in 2019 we will start to see the end of this relentless, frustrating assault on CSS. The pessimist in me says that it’s only just beginning because we’re in an industry that is quickly resembling the bloated, proprietary, dependency ridden software development culture of the corporate world, rather than the lean, flexible and open nature of the web.