(info.arxiv.org)

262 points el3ctron | 1 comments | 06 Dec 25 14:59 UTC | HN request time: 0.196s | source

Show context

percentcer ◴[06 Dec 25 20:06 UTC] No.46176216[source]▶

Dumb question but what stops browsers from rendering TeX directly (aside from the work to implement it)? I assume it's more than just the rendering

replies(2): >>46176253 #>>46176297 #

pwdisswordfishy ◴[06 Dec 25 20:11 UTC] No.46176253[source]▶

>>46176216 #

For starters, TeX is Turing-complete, and the tokenizer is arbitrarily reprogrammable at runtime.

replies(3): >>46176306 #>>46176542 #>>46181967 #

1. gbear605 ◴[06 Dec 25 20:57 UTC] No.46176542[source]▶

>>46176253 #

Browsers already support JavaScript anyway, so why not add another Turing-complete language into the mix? (Not even accounting for CSS technically being Turing-complete, or WASM, or …)

↑

HTML as an Accessible Format for Papers (2023)