firefox

I took a brief gander at its code [0] and saw it mainly focusses on k-means clustering algorithms (in JS, no less). To my ken this is likely for suggesting new tabs, something a user is even less likely to use than renaming them. Its constant drain even when not 'in use' seems to imply it's classifying tabs as they change page (though it might be telemetry or uncommented testing). If so, it's an example of premature optimisation gone very wrong. It's a shame, because it overshadows the fact that naming tab groups is a perfect use case for an LLM, alongside keyboard suggestions and reverse dictionaries [1]. I'm ardently distrustful of LLMs for many, many purposes, but for the tiny parameter and token usage needed it's hard to not like. Which is a shame it's (somehow) such a drain. [0] https://github.com/mozilla-firefox/firefox/blob/7b42e62

Fwiw the XSLT implementation in Blink and WebKit is extremely inefficient. For example converting the entire document into a string, to parse it to a format that's compatible with libxslt, to then produce a string and parse it back into a node structure again. I suspect a user space library could be similarly as effective. Ex. https://source.chromium.org/chromium/chromium/src/+/main:thi... https://source.chromium.org/chromium/chromium/src/+/main:thi... https://github.com/WebKit/WebKit/blob/65b2fb1c3c4d0e85ca3902... Mozilla has an in-house implementation at least: https://github.com/mozilla-firefox/firefox/tree/5f99d536df02... It seems like the answer to the compat issue might be the MathML approach. An outside vendor would need to contribute an implementation to every browser. Possibly taking the very inefficient route since that's easy t