OWASP’s cheat sheets are really good for quickly learning
about web security gotchas.
The load averages here appear nominal, so perhaps my servers haven’t been disembodied just yet.
In fact, one can sus out the “true” APIs of anything by analyzing a company’s
repositories for usages (Mozilla, Google, Apple). This allows you to
guess at deprecations,
wrongly.
I’m not an person, but if
XSL transformations are interesting (like to
Markdown),
look at Paligo/xee
(Rust). I think I wrote about extensible stylesheets
(and Saxonica) somewhere after
being impressed by XML pros in action.
PHP 8 has an
actual HTML5 parser now.
Who’d have thought? This kind of thing (I guess) is better late than never.
There are so many things that I can go back to now and simplify the hell out of.
I heard of
another static site generator.
“Static sites” are not really my jam, but are economically fun. I might try
templating that one.
Its motivation
adds to my hunch that golang templating is generally
disliked. I’m occasionally asked about go (online), but I know very little
actually.
I unfortunately recommended a Firefox addon somewhere. Maybe it
(Disable JavaScript)
or some versions of it got hacked/backdoored because
the repository just up and
poofed
itself. Luckily, Firefox isn’t that popular.
Addon files are usually zips and
CRX Viewer
is good for corner peeking. I look around corners thrice,
occasionally, sometimes, maybe?
I’ve just learned something the hard way. There’s stuff out there that spins
console.clear()
and debugger
in infinite loops. I don’t know why that’s a thing but I like to call it: clear
console log debugger abuse.
It’s amazing how trends in modern mainstream web development have seemingly
inverted. One such example (an old bookmark) while following tech more closely
in school;
Therefore by purposefully giving the user a blank page, we are giving him
information that the app is still loading. The user knows that the app will be
functional when he sees boxes and buttons.
The truth was it didn’t matter, at least, not so much as “position independent
code”, kind of. Tech appears to do a ten year amnesiac/discovery routine.
Web components
arrived around that time too.
The best
CSS Framework? I
don’t know. Complexity moves in mysterious ways. The many interpretations
model must be satisfied.
in CSS (canonical)
CSS in (write once and time driven)
CSS in JavaScript (framework driven)
CSS in Shadow (company/department driven)
CSS in Scoped Formats ( driven)
CSS in Preprocessors (design system driven)
I’d say, choices reflect environmental factors (social or otherwise) at play. If
you’re lucky enough to choose, then suitability favors what draws the finish
line closer?
I’ve no advice since I’d rarely have the time/luxury to choose anyway. I’m
usually thinking about the possibility of more types, sub–types
( in #1: ,
classless, etc), and the transposition
strategy and speed between each class/type.