<p>hey hhoommee<br /><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span></p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> oh yeah, the whole point is that there isn&#39;t a compiler it&#39;s shelling out to under the hood, right? Zig just links all of clang in to make this work. I wonder if LLVM has an output abstraction layer and zig just has a really dumb implementation of it? I am curious about how many times it&#39;s actually calling write(0, …), though!</p>

<p>I even put on my fun shirt like it is picture day.</p>

<p>The next 10 years of travel with this plus one</p>

<p>Trying to decide if I&#39;m going to get passport photos taken after work today or if I should wait until this zit on my chin goes away.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@tedmielczarek" class="u-url mention">@<span>tedmielczarek</span></a></span> i suspect there may be pipes involved</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mntmn" class="u-url mention">@<span>mntmn</span></a></span> ooooooh</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> you unlocked multiball! But seriously: getting per-character interleaving like that requires going out of the way to do weird things. glibc line-buffers output by default. Even on Windows—which has the worst default behavior—output is buffered in chunks of 1KB or so. Is something in there really writing a byte at a time to stdout without buffering???</p>

<p>Admitted to the kid that thinking about college is actually freaking me out a bit.</p><p>&quot;Why&#39;s that dad?&quot;</p><p>&quot;Because I&#39;m still trying to figure out what *I* want to do.&quot;</p>