[lelandfe]

Bingo. Author will be fighting an uphill battle on HN because of the lack of specificity (an appropriate problem for a CSS article)

[matsemann]

Or people could just read the very short article instead of instantly assume stuff based on the title here.

[lelandfe]

The article's own title is "Margin considered harmful" and the body finishes with the sentence "Ban margin."

[tinus_hn]

The use of the ‘considered harmful’ trope should tell you al you need to know.

[laumars]

I did read the article and frankly it’s little better than the HN title. It’s heavily biased, fails to offer a convincing argument to anyone other than those who already believed the title, and even explicitly says margins should be banned.

Simply put, it’s not a good article.

[Veen]

> It’s heavily biased

What does "heavily biased" mean in this context? It's a straightforward article that puts forward a position, a series of propositions supporting that position, and a potential solution.

It's biased in that the author has an opinion he's trying to convince people of by providing arguments in its favour, but that's what writing tends to do (including your comment).

The "banning" stuff is obvious hyperbole[0]. No reasonable reader could conclude the writer means CSS margins should be banned in law.

[0]: https://en.wikipedia.org/wiki/Hyperbole

[laumars]

You’ve admitted yourself that the article is highly opinionated and full of hyperbole so I don’t really see why you’re confused by my statement. But I’ll answer your question nonetheless.

Any article stating something should be “banned” can’t really be described as a balanced discussion about the usage of that thing.

I’m all for discussions on why usage of something is bad but in the case of margins there’s clearly use cases that are suited to it, which other commenters have highlighted but which the article entirely glossed over.

So the article is more than just written as a persuasive piece; it misses any balance or contextual clarity and thus ends up dishing out bad advice as a result. Bad advice that is so strongly emphasised that lesser experienced developers would easily be intimidated by it.

Now if people want to discuss the strengths and weaknesses of margins and put forward alternative solutions in the process, that at least informs lesser experienced developers about ways to solve their real world problems rather than berating them for not following some misguided idealised view of perfection.

(Yes I know there was some details about alternative ways to implement a margin, but they were crap and lacked any detail, since the article was essentially a rant piece rather than technical document)

[andy_ppp]

Good luck with that…

[stepbeek]

This made me laugh out loud. Thank you.