# Should complexity formatted as code be updated to use MathJax?

I saw a post that mentions algorithmic complexity and formats such complexity values using inline code spans (e.g. O(n)). Should that post be updated to use MathJax formatting, since that is an option instead of inline code spans?

• Heavy mathjax usually slows done page rendering. On stackoverflow it is a real problem for me, as it is more "fast paced". The only problem I see with it on CR is that not everyone is familiar with it. I still cannot write anything complicated without a cheatsheet. – Incomputable Dec 17 '17 at 8:54
• The only other argument I could think of is what happened on ppcg: the mathjax got removed after a point. But here on codereview, it doesn't seem like that will be a problem, seeing as the mathjax was added quite some time ago. – Justin Dec 18 '17 at 8:52
• A downside to MathJax is that it involves 3rd-party Javascript; it's not obvious that enabling another site will make the post more readable. – Toby Speight Dec 20 '17 at 10:33

Why not? Especially if there's more to edit than just a single instance of O(n)... I presume screen readers treat MathJax differently than inline code, too.
I'd probably leave alone an otherwise clearly worded, correctly formatted post without any typos and just that single O(n) though.
I have mixed feelings about mathjax for BigO notation in lieu of BigO notation as code. Mathjax makes writing and editing BigO notation harder without significantly improvements to clarity.
In short, I don't see what problem editing BigO notation from code to MathJax solves. I see several potential usability problems it creates for people without LaTeX experience: i.e. the vast majority of people.