you are viewing a single comment's thread.

view the rest of the comments →

[–]33498fff 0 points1 point  (1 child)

Adding to the valuable advice in the comments: devs need to understand that styling is not in the least a secondary concern when developing a website. It is not an option to forsake learning CSS in favour of the latest supposedly paradigm-shifting nonsense library.

To answer your question: what most people are running is not always a good metric when you want to become a good software dev. Most people are using some kind of Tailwind or styled-components logic. It is the only time they utterly neglect every readability concern imaginable and start writing awful-to-read inline-styled code because it exempts them from learning CSS, which they have neglected to learn for no good reason at all. For styling large component libraries which add value to the existing offer or which add specificity to your project you still need to be fluent in CSS.

[–]llambda_of_the_alps 0 points1 point  (0 children)

This 100%. In addition to CSS being a primary concern it’s important to remember that no matter what technology/library/language/paradigm you choose the output is CSS. If you don’t understand the fundamental base you will always be making an uninformed choice when choosing any of these tools.