If I knew how to design a layout engine that wouldn't become a giant pile of HTML+CSS like cruft I'd honestly do it myself. I know how to make a bytecode VM with JIT that handles rendering, audio, video, networking, and input, because that's what game engines are
Anyway at this point if you ask me browsers are just VMs with a layout engine except done in the absolute worst way possible
Making 8-bit Music From Scratch at the Commodore 64 BASIC Prompt by lftkryo
https://www.youtube.com/watch?v=ly5BhGOt2vE
ALL THESE YEARS HEARING ABOUT AUTOMATTIC AND MATT MULLENWEG AND I NEVER REALISED HE WAS VAIN ENOUGH TO NAME THE COMPANY AFTER HIMSELF!!! 😭
If the Kubernetes material was honest about "your team will need recurrent annual training to remain current with this tool," adoption would crater overnight.
That's not unique to Kubernetes, though it is fun to pick on them for it. _Nearly every_ significant infrastructure tool has this shape. Organizations that adopt these tools are unable to receive their value until their staff know how to use them, and that knowledge is deeply not self-sustaining.
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess