That's a valid concern, especially given the confusion we saw with .zip or .mov TLDs. But from a security engineering perspective, the bigger 'Markdown hole' I worry about is injection. When we render untrusted AI output into HTML for email, the sanitization pipeline becomes critical. I'd be curious to see how this library handles potential XSS vectors during the MD-to-HTML conversion.
The last time I did this was very long ago, but still I was surprised that of all things, the WiFi didn't work (some Intel issue). Newer laptops also have "accessories" such as fingerprint reader, touch bar etc which may not be trivial to get to work.
And anyways, the interesting part of the link for me was official collaboration from Dell, although I couldn't fit it within the title.
My take is a Dell can be pretty good but things like the fingerprint readers will often be busted even on Windows. I expect some things to be busted on a Dell and I'm not going be like those mac-ers who go to the genius bar 50x because there is some small thing like a fingerprint reader that 'just doesn't work'.
SwiftLatex, TexLyre and StellarLatex seem to be exactly this. Apparently this is something a lot of people want to see in the world, awesome stuff. I wonder what's the performance like between native XeLaTex and these wasm version and if it will be Overleaf's demise if these solutions can be easily self-hosted by organizations without worrying about the server getting bogged down by compile jobs.
You can do that with Onnx. You can graft the preprocessing layers to the actual model [1] and then serve that. Honestly, I already thought that ONNX (CPU at least) was already low level code and already very optimized.
@Author - if you see this is it possible to add comparisons (ie "vanilla" inference latencies vs timber)?
Anyways, I really appreciate you created the post. It’s pretty amazing that a project from a self-taught developer like me, who started in 2024, got so much attention.
reply