I really enjoyed this post, mostly since I've come upon the same view lately.
Most elements in web development nowadays is simply divs stuffed with mountains of classes, and it makes it very annoying to debug, read, or edit.
Frontend frameworks aren't exactly helping the situation either; everything is a component and there's no need to use anything other than divs, but it takes away from the accessibility and understanding of the code.
However, I won't say I'm not guilty of this. Using divs often seems easier than trying to decide whether to use a section, article, or whatever else, and has established itself as a generic element that can be used anywhere. But the downsides are clear, and many web developers (including myself) should strive to use the markup we're provided.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really enjoyed this post, mostly since I've come upon the same view lately.
Most elements in web development nowadays is simply
divs stuffed with mountains of classes, and it makes it very annoying to debug, read, or edit.Frontend frameworks aren't exactly helping the situation either; everything is a component and there's no need to use anything other than
divs, but it takes away from the accessibility and understanding of the code.However, I won't say I'm not guilty of this. Using
divs often seems easier than trying to decide whether to use asection,article, or whatever else, and has established itself as a generic element that can be used anywhere. But the downsides are clear, and many web developers (including myself) should strive to use the markup we're provided.