Live data from Hacker News

TikZJax: Embedding LaTeX Drawings in HTML

tikzjax.com

1–10 of 33 posts

Re: TikZJax: Embedding LaTeX Drawings in HTML

#4
Jim Fowler seemed like Calculus' biggest hype man when the MOOC ball was just starting to roll. If you're looking to brush up and like the more energetic/engaging style I'd recommend checking out his videos on YouTube or elsewhere.

> Using web2js, the Pascal source of tex is compiled to WebAssembly; the latex format is loaded (without all the hyphenation data), and [...] is executed. Then core is dumped; the resulting core is compressed, and by reloading the dumped core in the browser, it is possible to very quickly get to a point where TikZ can be executed. By using an SVG driver for PGF along with dvi2html, the DVI output is converted to an SVG.

This is the kind of hack I'm here for.

Re: TikZJax: Embedding LaTeX Drawings in HTML

#5
post #3
post #2

Hm. Either that page or the tech itself is not great on mobile.

Takes a second or so to load on mine (iOS Safari). But then it shows correctly, even if the second diagram is a bit small (it fits in a quarter of the 1in circle).

It crashes (“a problem repeatedly occurred”) a few seconds after loading everything on my device (also iOS Safari).

I love tikz, but lightweight it is not; it’s not a huge surprise it takes a few seconds to render.

No idea what’s causing the crash, though.

Re: TikZJax: Embedding LaTeX Drawings in HTML

#6
Using a “core dump” (dumping the webassembly heap) is an interesting optimization approach with historical precedent both in TeX itself and projects like Emacs (dump/unexec) — https://www.gnu.org/software/emacs/manual/html_node/elisp/Bu...

It’s also notoriously fragile and non-portable on native targets; I’m curious how one implements it under webassembly, and how it compares.

Re: TikZJax: Embedding LaTeX Drawings in HTML

#7
post #3

Earlier quoted context omitted.

Takes a second or so to load on mine (iOS Safari). But then it shows correctly, even if the second diagram is a bit small (it fits in a quarter of the 1in circle).

It crashes (“a problem repeatedly occurred”) a few seconds after loading everything on my device (also iOS Safari). I love tikz, but lightweight it is not; it’s not a huge surprise it takes a few seconds to render. No idea what’s causing the crash, though.

Well iOS Safari is in general buggy and tends to display the "a problem repeatedly occurred" message on many other slightly heavy web pages. This web page shouldn't be blamed for causing Safari to crash.

Re: TikZJax: Embedding LaTeX Drawings in HTML

#8
post #7

Earlier quoted context omitted.

It crashes (“a problem repeatedly occurred”) a few seconds after loading everything on my device (also iOS Safari). I love tikz, but lightweight it is not; it’s not a huge surprise it takes a few seconds to render. No idea what’s causing the crash, though.

Well iOS Safari is in general buggy and tends to display the "a problem repeatedly occurred" message on many other slightly heavy web pages. This web page shouldn't be blamed for causing Safari to crash.

Nobody is assigning blame, we don’t know the root cause.

I could just as easily say that Safari shouldn’t be blamed for a buggy website, but I’d be overreaching just as much as you just did.

Re: TikZJax: Embedding LaTeX Drawings in HTML

#9
post #7

Earlier quoted context omitted.

Well iOS Safari is in general buggy and tends to display the "a problem repeatedly occurred" message on many other slightly heavy web pages. This web page shouldn't be blamed for causing Safari to crash.

Nobody is assigning blame, we don’t know the root cause. I could just as easily say that Safari shouldn’t be blamed for a buggy website, but I’d be overreaching just as much as you just did.

By definition buggy websites that crash the browser are bugs in the browser.

It may have security implications, or it may not. It might just be an innocent case of someone using assertions instead of proper error reporting. Nevertheless it's a bug in the browser.

Re: TikZJax: Embedding LaTeX Drawings in HTML

#10
post #9

Earlier quoted context omitted.

Nobody is assigning blame, we don’t know the root cause. I could just as easily say that Safari shouldn’t be blamed for a buggy website, but I’d be overreaching just as much as you just did.

By definition buggy websites that crash the browser are bugs in the browser. It may have security implications, or it may not. It might just be an innocent case of someone using assertions instead of proper error reporting. Nevertheless it's a bug in the browser.

Safari will terminate a page for using excess resources with the same message.
Post reply on HN