<p>OH: &quot;Cat convinced me to do it like that. I considered it completely batshit at first, then it dawned on me that it&#39;s actually the only reasonable way to do this&quot;</p>

<p>The recent issue with matrix signing keys (<a href="https://hdev.im/@farcaller/114043928830424018" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">hdev.im/@farcaller/11404392883</span><span class="invisible">0424018</span></a>) got me thinking why I don’t like rust (in which conduit is written). <a href="https://hdev.im/tags/Rust" class="mention hashtag" rel="tag">#<span>Rust</span></a> is very hard to reason with at glance.</p><p>If you don’t have an LSP at hand, you can only vaguely figure out which types are where. It&#39;s pretty much impossible to go from a method call to its implementation by name alone. The code is messy with various symbols and evokes the feelings of dread^W perl.</p><p>Compare that with go. The code is arguably full of boilerplate, but it&#39;s an easy to read boilerplate. I got asked about kube-controller-manager recently and I just went to k8s sources, found the init loops and reasoned with what KCM does within minutes.</p><p>Every time I need to touch the lemmy source code I feel like finding ways to aviod it. Sure rust has its benefits, it&#39;s fast and efficient and so hard to just read.</p>

<p>Absolutely no wind this morning, so we braced the main around and hove to.</p>

<p>Had a quiet night watch since there was almost no wind.</p>

<p><span class="h-card" translate="no"><a href="https://is.badat.dev/users/meithecatte" class="u-url mention">@<span>meithecatte</span></a></span> hey</p>