<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@timonsku" class="u-url mention">@<span>timonsku</span></a></span> <span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> A Shahed? But those run on bodge standard AliExpress Artixes and Kintexes, judging from what I saw on photos.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@timonsku" class="u-url mention">@<span>timonsku</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> Yep, that seems very plausible for a gov customer.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://ioc.exchange/@azonenberg" class="u-url mention">@<span>azonenberg</span></a></span> then I would say very likely that it was a custom run without markings to obfuscate what specific part it is. I think you likely have the correct family given how identical that heat-spreader is.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@dabeaz" class="u-url mention">@<span>dabeaz</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@deshipu" class="u-url mention">@<span>deshipu</span></a></span> <span class="h-card" translate="no"><a href="https://hachyderm.io/@robpike" class="u-url mention">@<span>robpike</span></a></span> </p><p>:-) Not really a fixed-point, no, I wasn&#39;t thinking of anything deep! I meant it more like n^n, pain for the sinner is amplified twice, in the base (there&#39;s an extra plague, namely types) and in the exponent (all plagues are typed).</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@headius" class="u-url mention">@<span>headius</span></a></span> dunno, my Rust code from 1.0 era still compiles and runs correctly and that is a breath of fresh air compared to just about any other language. I think disregarding this option is a failure of imagination</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> All code faces the infinite upgrade treadmill unless they freeze library and runtime dependencies, in which case the removal of deprecated APIs doesn&#39;t matter. I will grant there&#39;s cases where some pattern becomes too pervasive to remove, but I believe the goal should always be removal of discouraged features.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@timonsku" class="u-url mention">@<span>timonsku</span></a></span> i figured as much</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@headius" class="u-url mention">@<span>headius</span></a></span> &quot;Once in a while&quot; doesn&#39;t make a platform crumble, and you also don&#39;t have to pile features on forever. I don&#39;t agree that an infinite upgrade treadmill is always desirable.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> All acceptance processes fail once in a while, and again, on a long enough timeline, those failures will accumulate unless you can remove them.</p>