Tools like KaTeX output both HTML and MathML simultaneously (HTML for rendering, MathML for screen readers), leading to massive page bloat. MathJax requires client-side JS to look good, which is a big 'no' for me.
Right now, there is no way to display math on the web that: (1) is accessible, (2) works across all modern browsers, (3) is not slow or bloated in some way. MathML in Chrome fixes basically all these problems.
This sort of dictating opinions via tech seems common in the browser world, and it honestly makes me thankful we primarily target pdfs and not the web.
Why I think LaTeX "won out":
1) Chrome dropped MathML 10ish years ago
2) MathJax got LaTeX support
3) People don't care about accessibility/ambiguity enough to bother with anything else
4) There aren't good, mainstream frontends for MathML other than MathType, making LaTeX more convenient to learn and use
Latex is basically the mathematical (computer) lingua franca right now. Theres an entire cultural and technological ecosystem around latex thats been built up for many years. We even message each in latex notation when rendering isn't available! Theres decades of documentation online. Most important of all, its dead easy to use for most use cases!
Perhaps MathML is technically superior in some ways, but none that the people typesetting math are concerned with. That this is browser oriented tech in particular is already a disadvantage, as the browser is not a priority to us. In this way mathjax feels like the superior tool for users. It attempts to work with users rather than dictating to them.
XML apologists generally propose special editors to make the experience less unpleasant, but that's not what working users of mathematics want.
TeX notation provides a way for us to type formulae in plain text form, anywhere that ascii is accepted, as fast as we can type normal text. That's the bare minimum required for any representation to be relevant to mathematicians and physicists.
I don't know what a more 'web flavoured' notation satisfying this constraint would look like. (Are web standards people even capable of brevity?)
> Latex packaging is nightmare.
and
> Verbosity will be solved by tones of JS and python packages.
seem at odds to me.