What I Mean By Using HTML And CSS Properly — Part 1 of 3
<p>I’ve talked a good deal in my articles and on various forums about how the <strong>creators</strong> of many things people add to their development stacks —<em> such as HTML/CSS “frameworks” like Bootcrap and “it’s not a framework” Failwind </em>— never learned enough about HTML or CSS to even be telling others how to use web technologies.</p>
<p><strong>I’m not being flippant or unnecessarily cruel in that.</strong> This is the truth. Truth hurts. And truth is these systems do more damage than good despite all the wild unfounded claims of merit attributed to them. <broken record><em>They are </em><strong><em>not </em></strong><em>“easier”, they are </em><strong><em>not </em></strong><em>“better for collaboration”, they do </em><strong><em>not </em></strong><em>“speed up development”, or any of the other bald faced lies found in the propaganda, fallacies, group-think, echo-chambers, and mob mentality behind their adoption.</em></broken></p>
<p>The same goes for a lot of people complaining about how HTML works when they’re in the same broken mindset as framework developers; which is to say having crammed one’s cranium up 1997’s rectum in worship of the all-mighty HTML 3.2 <strong>mental</strong>ity. <em>Emphasis on the “mental”</em></p>
<p>And as I keep saying if you understood even the simplest of reasoning behind why HTML exists; why CSS stands apart from it; and the entire reason for why web stacks are the way they are? They’d recoil in horror at how stupid, ignorant, and painfully convoluted the way most people write HTML is.</p>
<p><a href="https://medium.com/codex/what-i-mean-by-using-html-and-css-properly-part-1-of-3-44804722e33a">Click Here</a></p>