For some time we’ve heard anti-vaxxers, Trump supporters, Libertarians, and others complaining about how their “rights” are being violated. The loudest of which seems be those incapable of social virtues; much less describe what rights are, why they are important, and more importantly where they end.
Rights are not carte-blanche to run around like a greedy narcissistic sociopath, no matter how hot and trendy that behavior is in society at the moment.
The simple fact is that most of those screaming loudest about their “rights” in American society have no clue what they’re talking about.
The dictionary definition always left me a bit wanting. Even as a child I didn’t feel that it truly encompassed the important concepts of it. Still, we must review this as a starting point. …
The majority of people are “visually oriented”. They like to think about how things look before most other concerns. When it comes to web development this is a hard “habit” to break oneself of, but it’s an essential one given that HTML is for more than just perfectly sighted users. It’s why bass-ackward nonsense like artists under the DELUSION they’re “designers” pushing pixels around in Photoshop are able to sucker nubes and rubes alike, flipping the bird at UX and accessibility in their ignorance of anything other than art. …
Yet frustratingly the one transition that’s hard to do is between “0” and “Auto” values. The automatic size calculation — sizing to the content — simply isn’t something browser makers seem to be willing to even consider implementing.
In my voyages from company to company as a freelance accessibility and efficiency consultant, I am constantly butting heads with web developers who have some genuinely queer notions of what semantic markup is and isn’t. From those saying “Isn’t that just for SEO?” to “It really doesn’t matter”, to “Well that’s just for coders to look at”, there’s a lot of disinformation, misunderstandings, and just plain lies out there.
To put it as plainly and succinctly as possible:
Semantic markup is nothing more than a sick euphemism for “Using HTML properly!”
Semantic markup is the reason HTML existed from the start. It’s not “just for SEO” since it had semantics two years before JumpStation — the first “real” HTML based search engine — was a twinkle in Feltcher’s eye. …
I want to like BEM — Block, Element, Modifier — I really do! Any time someone comes up with a uniform consistent naming scheme, I’m usually all-in… BUT… when it comes right down to it how it works and what it does defeats most if not all of why HTML exists and why CSS is separate from it.
It reeks of people too stupid to understand the simplicity of selectors, combinators, and proper semantics trying to just slop classes everywhere to fix their own ineptitude; when really if using combinators and the proper markup is “so hard” you need this stuff, maybe it’s time to give up, walk away, and go flip burgers for a living. …
In part 1 I showed how to take someone else’s simple example, and give it a bit of spit and polish cutting the code size almost in half. Since it was already tiny, that now gives us room to enhance it with more functionality.
In particular the use of two objects containing our sort types and data gathering methods lays the groundwork for easily adding more types of sorts.
To show off our new filters we need a new table with new data.
The table caption/header is where most of the changes take…
There are a number of decent articles out there about doing this. In particular, Bobby Jack’s article here on Medium stands out for a few reasons:
Note, sorry but this article is going to skip between languages a bit.
Everyone knows about
foreach. They’re the staple of programming array loops. If you work in PHP, you likely know what they do and how to use them…
But what about
Much less how
while can be used to smartly make loops in most all C syntax languages?
I’ve been shocked the past year or so how many dev’s I come across who’ve never even heard of them, much less understand their use. What prompted this article is that I was just working on a “function stack” of anonymous that other processes can add to, and I used this because of the “You can’t add to an array inside a foreach” issue; and a colleague saw it and said “what the devil is that?!?” …
Over on DigitalPoint it was asked if it were possible to make a clock face using just HTML and CSS. Whilst I answered their question as cleanly as I could in a drive-by answer, I thought a more polished and robust copy would make a good article.
Ever since HTML 5 was introduced I’ve bemoaned how it undoes so much of the intent and good practices of HTML 4 Strict.
New redundant tags like <section>, <header>, <video>, and <audio>. Elements like <embed> that should NEVER have been allowed into HTML in the first place. Etc, Etc.
They even introduced — then quickly deprecated — the <hgroup> tag proving the WHATWG didn’t know enough HTML to be making the new specification!
Don’t get me wrong there are a number of improvements, or things I can live with even if I don’t 100% approve…
But over the past ten years it feels like every blasted month I find one more thing that makes me want to tell the W3C to suck it. …