The biggest issue is the lack of tooling and the inability to manage a shared state. We actually ended up creating new libraries like Stencil & Lit.

Custom Elements missed the mark with the problem frameworks solve. We don't necessarily need custom HTML, we needed easy way to build and manage the whole data and visual flow locally while treating the backend response as a datasource.

Nowadays, I use web components for one-off, isolated components as a replacement for iframes, but rarely for anything complex.

I think you misunderstand.

Taking notes during meetings isn't to improve understanding, or to "read" afterwards.

They're a record of what was discussed and decided, with any important facts that came up. They're a reference for when you can't remember, two weeks later, if the decision was A and B but not C, or A and C but not B.

Or when someone else delivers the wrong thing because they claim that's what the meeting decided on, and you can go back and find the notes that say otherwise.

I probably only need to find something in meeting notes later once out of every twenty meetings. But those times wind up being so critically important, it's why you take notes in the first place.

On the positive side of this, research papers by competent people read very clearly with readable sentences, while those who are afraid that their content doesn't quite cut it, litter it with jargon, long complicated sentences, hoping that by making things hard, they will look smart.

But to expand on the spelling topic, good spelling and grammar is now free with AI tools. It no longer signals being educated. Informal tone and mistakes actually signal that the message was written by a human and the imperfections increase my trust in the effort spent on the thing.