---
title: "Comment by Mihai Deta on \"DRY HTML or DRY CSS? 🤯\" | Hashnode"
description: "well... interesting... but i don;t think you offered enough information on this methodology ... I'd go for BEM for css, its usefull when you use sass or les"
url: "https://hashnode.com/posts/dry-html-or-dry-css/5c94e11e1e0fb7505b9b1093/comment/5c965e35c5c8c901317c781c"
---

[Discussion](https://hashnode.com/posts/dry-html-or-dry-css/5c94e11e1e0fb7505b9b1093)

Comment [DRY HTML or DRY CSS? 🤯](https://hashnode.com/posts/dry-html-or-dry-css/5c94e11e1e0fb7505b9b1093)

[Mihai Deta](https://hashnode.com/@mihaid)

[Mar 23, 2019](https://hashnode.com/posts/dry-html-or-dry-css/5c94e11e1e0fb7505b9b1093/comment/5c965e35c5c8c901317c781c)

well... interesting... but i don;t think you offered enough information on this methodology ... I'd go for BEM for css, its usefull when you use sass or less, it keeps your classes organized. But DRY on html... so you;re telling me i should make a template for every element i need on a page? NO! i won't do that. i don;t want to make my application harder to read/modify. But i think this DRY thing is usefull but you have to determine what arhitecture your application will have before using it.

NOTE: i know this isn;t important, but, when using ems or rems, write the fallback for them in pixels, just for older browsers, antic ones and maybe safary

[Pankaj Patel](https://hashnode.com/@pankajpatel)

[Mar 23, 2019](https://hashnode.com/posts/dry-html-or-dry-css/5c94e11e1e0fb7505b9b1093/comment/5c965e35c5c8c901317c781c#reply-5c96798d84f88cb846bf475a)

Thanks for your feedback. These days I am trying to step away from LESS, SASS and moving more towards PostCSS. And BEM, OOCSS or similar structure is very powerful from the maintenance perspective, though I prefer writing small CSS class-names.

Along with that, the post was written from HTML perspective as well. As these days components are more common, the example is about Component approach with web components where thinking in terms of components will make sense to have a template for app-specific components rather than elements.

Regarding the use of `em`s; can not fallback to the pixels as the value of em is dependent on the parent element's font size. For `rem`s, the CSS processor like LESS, SASS or PostCSS takes care of that.