最新

I’m researching patterns for edge &#x2F; gateway telemetry where the network is unreliable (remote sites, industrial, fleets, etc.) and you need offline buffering + bounded disk + replay once connectivity returns.<p>Questions for folks running this in production:<p>What do you use today? (MQTT broker + ??, Kafka&#x2F;Redpanda&#x2F;NATS, Redis Streams, custom log files, embedded DB, etc.)<p>Where do you buffer during outages: append-only log, SQLite&#x2F;RocksDB, queue-on-disk, something else?<p>How do you handle backpressure when disk is near full? (drop policy, compression, sampling, prioritization)<p>What’s your failure nightmare: corruption, replay storms, duplicates, “stuck” consumer offsets, disk-full, clock skew?<p>What guarantees do you actually need: zero-loss vs “best effort” (and where do you draw that line)?<p>What metrics&#x2F;alerts matter most on gateways? (queue depth, replay rate, oldest event age, fsync latency, disk usage, etc.)<p>I’d love to learn what works, what breaks, and what you wish existing tools did better.

Hi HN, author here.<p>I built Tylax because I wanted to migrate my old LaTeX papers to Typst but found existing regex-based scripts too fragile for nested environments.<p>Tylax parses LaTeX into an AST (using mitex-parser) and converts it to Typst code. It supports: - Full document structure (not just math snippets) - Complex math (matrices, integrals) - Experimental TikZ -&gt; CeTZ graphics conversion - Runs in browser via WASM<p>Repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;scipenai&#x2F;tylax" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;scipenai&#x2F;tylax</a> Web Demo: <a href="https:&#x2F;&#x2F;convert.silkyai.cn&#x2F;" rel="nofollow">https:&#x2F;&#x2F;convert.silkyai.cn&#x2F;</a><p>Happy to answer any questions!