Things I would like every young web engineer to learn:
- anything you can do in CSS + HTML, you *should* do in CSS + HTML
- *framework du jour* is not a platform, it's a high-interest loan against your future capacity. The platform is the platform
- understanding the memory hierarchy *always* matters
- client-side isn't easier than the server, and "generalists" usually suck at client-side. Mind the (packet) gap
- managers who are not technical are not useful
- put users first, always
“Pants on Fire – Pixel Envy”
"But Evans does not give nearly enough weight to how often big industry players and their representatives simply lie."
I’m shocked, shocked etc. etc. https://pxlnv.com/blog/pants-on-fire/
nostr:npub16u7alxzkjugh6535altqqk5gx7g0a63x6m300l898nenys0rsjuqguuend It may come as little shock to you that one of the primary modes Apple uses in arguments against browser competition (when not generously funding astroturf lobbying groups) is to simply mislead regulators, through lawyers who plausibly (and probably) don't know better.
The year is Anno Domini MMXXIII.
The Paper of Record produces news, but wraps it in megabytes of JavaScript to keep the poors from becoming incidentally informed.
What cover story is floated?
In part, that it is necessary, in browsers with pervasive support for Web Crypto[1], to include a userland SHA-256 hashing routine.
In truly dark ages, such barbarism is considered normal.
[1]: https://caniuse.com/cryptography
