<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sparse Attention on MacWorks</title><link>https://macworks.dev/tags/sparse-attention/</link><description>Recent content in Sparse Attention on MacWorks</description><generator>Hugo</generator><language>en</language><atom:link href="https://macworks.dev/tags/sparse-attention/index.xml" rel="self" type="application/rss+xml"/><item><title>Engineer Reads</title><link>https://macworks.dev/docs/today/engineer-blogs-2026-06-18/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://macworks.dev/docs/today/engineer-blogs-2026-06-18/</guid><description>&lt;h1 id="engineering-reads--2026-06-18"&gt;Engineering Reads — 2026-06-18&lt;a class="anchor" href="#engineering-reads--2026-06-18"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="the-big-idea"&gt;The Big Idea&lt;a class="anchor" href="#the-big-idea"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The friction between idealized abstractions and hardware realities constantly forces engineers to compromise. Whether you are battling the hidden, non-deterministic state of C++ build toolchains or applying sparse attention to make massive LLM context windows economically viable, the lowest layers of the stack inevitably leak into your application design.&lt;/p&gt;
&lt;h2 id="deep-reads"&gt;Deep Reads&lt;a class="anchor" href="#deep-reads"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="https://xeiaso.net/notes/2026/anubis-wasm-vendor-binary/"&gt;I hate compilers&lt;/a&gt;&lt;/strong&gt; · xeiaso.net
To maintain a single source of truth for proof-of-work checks without locking out users who have disabled WebAssembly, the author decided to compile their WASM logic to a JavaScript fallback using &lt;code&gt;wasm2js&lt;/code&gt;. However, bundling this tool exposed the brutal reality of reproducible builds: while compilers are theoretically deterministic functions, they are practically overflowing with implicit state. The post dissects how Clang secretly shells out to &lt;code&gt;$PATH&lt;/code&gt; dependencies like &lt;code&gt;wasm-opt&lt;/code&gt;, which can unexpectedly break builds if the host&amp;rsquo;s version lacks WebAssembly Exception support. Even more insidiously, Clang&amp;rsquo;s exception-handling code generation leaks raw memory pointer values into the output byte order, forcing the author to disable Address Space Layout Randomization (ASLR) and maintain separate architectural checksums. Any systems engineer relying on cross-platform C++ compilation or reproducible builds should read this for a sobering reminder of how brittle our build infrastructures actually are.&lt;/p&gt;</description></item></channel></rss>