<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: bonzini</title><link>https://news.ycombinator.com/user?id=bonzini</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 14 Apr 2026 10:10:38 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=bonzini" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by bonzini in "AI assistance when contributing to the Linux kernel"]]></title><description><![CDATA[
<p>The wording might be more or less lawyerly but the idea is fairly common, e.g. <a href="https://openinfra.org/legal/ai-policy" rel="nofollow">https://openinfra.org/legal/ai-policy</a> (OpenStack).</p>
]]></description><pubDate>Sat, 11 Apr 2026 18:06:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=47732689</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47732689</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47732689</guid></item><item><title><![CDATA[New comment by bonzini in "AI assistance when contributing to the Linux kernel"]]></title><description><![CDATA[
<p>Signed-off-by is a chain. The second person asserts that they delegate to the first person for the parts contributed by the first, and signs off on the ones that were contributed personally.<p>Hypothetically in court you'd go to the last, ask "did you write this" and only if not go up.</p>
]]></description><pubDate>Sat, 11 Apr 2026 18:05:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=47732678</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47732678</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47732678</guid></item><item><title><![CDATA[New comment by bonzini in "AI assistance when contributing to the Linux kernel"]]></title><description><![CDATA[
<p>You can write in AGENTS.md to ask the user for explicit sign off and to explain the document to the user.</p>
]]></description><pubDate>Sat, 11 Apr 2026 18:02:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=47732658</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47732658</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47732658</guid></item><item><title><![CDATA[New comment by bonzini in "Surelock: Deadlock-Free Mutexes for Rust"]]></title><description><![CDATA[
<p>Usually a global lock is a lock that is taken outside all others and is taken for large parts of the runtime (or even, everywhere the thread isn't waiting on a condition variable, file descriptor and the like).<p>Mutex::new(AppConfig::default()) might very well be a small, leaf mutex.</p>
]]></description><pubDate>Sat, 11 Apr 2026 17:48:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=47732538</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47732538</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47732538</guid></item><item><title><![CDATA[New comment by bonzini in "Moving from WordPress to Jekyll (and static site generators in general)"]]></title><description><![CDATA[
<p>I use a SSG for a conference. The git repository guides me in doing exactly the same changes every year. I have pre built blocks for the various stages of organization and go through the commits for the previous year to help me understand what to do next.</p>
]]></description><pubDate>Fri, 10 Apr 2026 04:16:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=47713578</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47713578</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47713578</guid></item><item><title><![CDATA[New comment by bonzini in "Show HN: M. C. Escher spiral in WebGL inspired by 3Blue1Brown"]]></title><description><![CDATA[
<p>You would have to know the position of the smaller copy in the uploaded image for the effect to work.</p>
]]></description><pubDate>Mon, 06 Apr 2026 04:59:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=47657164</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47657164</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47657164</guid></item><item><title><![CDATA[New comment by bonzini in "Show HN: M. C. Escher spiral in WebGL inspired by 3Blue1Brown"]]></title><description><![CDATA[
<p>It's cited by 3b1b themselves, who used Leiden's un-spiralized image to describe the effect.</p>
]]></description><pubDate>Sun, 05 Apr 2026 11:47:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=47648398</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47648398</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47648398</guid></item><item><title><![CDATA[New comment by bonzini in "IBM Announces Strategic Collaboration with Arm"]]></title><description><![CDATA[
<p>This certainly has been in the making for longer than the "everything we do must be for AI" bubble. In fact s390 has its own on-die inference engines and they have access to the same caching mechanisms as the main processor (which are quite insane).</p>
]]></description><pubDate>Thu, 02 Apr 2026 12:26:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=47613523</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47613523</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47613523</guid></item><item><title><![CDATA[IBM Announces Strategic Collaboration with Arm]]></title><description><![CDATA[
<p>Article URL: <a href="https://newsroom.ibm.com/2026-04-02-ibm-announces-strategic-collaboration-with-arm-to-shape-the-future-of-enterprise-computing">https://newsroom.ibm.com/2026-04-02-ibm-announces-strategic-collaboration-with-arm-to-shape-the-future-of-enterprise-computing</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47611721">https://news.ycombinator.com/item?id=47611721</a></p>
<p>Points: 282</p>
<p># Comments: 191</p>
]]></description><pubDate>Thu, 02 Apr 2026 08:48:44 +0000</pubDate><link>https://newsroom.ibm.com/2026-04-02-ibm-announces-strategic-collaboration-with-arm-to-shape-the-future-of-enterprise-computing</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47611721</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47611721</guid></item><item><title><![CDATA[New comment by bonzini in "Scientists crack a 20-year nuclear mystery behind the creation of gold"]]></title><description><![CDATA[
<p>It's about refining theoreticals models that are used to predict nucleosynthesis of heavier elements. The researchers used indium because we can obtain the required neutron-heavy isotopes for indium but not for heavier elements such as gold or platinum. But improving the model with data from indium, they say, makes it more accurate for gold as well?<p>Why then gold in the title? Probably just because it's shiny.</p>
]]></description><pubDate>Wed, 01 Apr 2026 21:40:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=47606870</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47606870</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47606870</guid></item><item><title><![CDATA[New comment by bonzini in "Monado became the foundation for OpenXR runtimes"]]></title><description><![CDATA[
<p>> The OpenGL model is having a specification that everyone implements, not a single foundational implementation??<p>They refer to Mesa. Otherwise unreadable I agree...</p>
]]></description><pubDate>Sun, 29 Mar 2026 13:54:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=47563167</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47563167</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47563167</guid></item><item><title><![CDATA[New comment by bonzini in "Looking at Unity made me understand the point of C++ coroutines"]]></title><description><![CDATA[
<p>Stackful coroutines also can't be used to "send" a coroutine to a worker thread, because the compiler might save the address of a thread local variable across the thread switch (happened in QEMU).</p>
]]></description><pubDate>Wed, 25 Mar 2026 23:36:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=47524791</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47524791</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47524791</guid></item><item><title><![CDATA[New comment by bonzini in "Slovenian officials blame Israeli firm Black Cube for trying to manipulate vote"]]></title><description><![CDATA[
<p>> If none of it mattered, why bother?<p>Hope for the best, plan for the worst. Republicans and missiles being the best.</p>
]]></description><pubDate>Wed, 25 Mar 2026 22:13:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=47523990</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47523990</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47523990</guid></item><item><title><![CDATA[New comment by bonzini in "Data centers are transitioning from AC to DC"]]></title><description><![CDATA[
<p>> all the inputs and outputs share the same ground, it's not just the values for that pair of wires?<p>No, it depends on the converter. There are converters that leave 160V on the DC power rail for a 110V AC input, and 155V on the DC "ground" rail.<p>They are economic and you could find then when galvanic isolation is at least in theory not important, but they're terribly unsafe when used on PCBs that people might muck with.<p>If you have some "normal" converters and some of this kind, sharing the ground would be quite dangerous.</p>
]]></description><pubDate>Wed, 25 Mar 2026 20:13:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=47522537</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47522537</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47522537</guid></item><item><title><![CDATA[New comment by bonzini in "An ode to bzip"]]></title><description><![CDATA[
<p>> meant to have good ratios and good (de)compression speeds as compared to other tools<p>That does not mean it's Pareto optimal; Pareto-optimality forms a curve and while zstd, LZMA, LZ4, ZPAQ all want to be as close as possible to the curve, they focus on different parts of it.  In particular zstd tries to stay on the middle part of the curve, while LZMA and LZ4 focus on opposite sides<p><pre><code>          ___.--- higher throughput
        /     LZ4
       / zStd
      |
      ; LZMA
     |
     | ZPAQ
    lower size
</code></pre>
Also, the Pareto curve is not necessarily known in advance. All you can do is add more and more algorithms or tweaks to understand what it looks like. For example, this blog post [<a href="https://insanity.industries/post/pareto-optimal-compression/" rel="nofollow">https://insanity.industries/post/pareto-optimal-compression/</a>] shows that prior to zstd, bzip2 and gzip2 were both pretty much Pareto optimal in the same area for ratio vs. compression speed. LZMA at low settings was a bit better but much slower. There was a huge gap between LZMA and LZ4, and bzip2/gzip filled it as best as they could.<p>The same blog post shows that zstd is an absolute speed demon at decompression; while not all zstd settings are Pareto optimal when looking at size vs compression speed (in particular LZMA wins at higher compression ratios, and even considering zstd only there's hardly a reason to use levels 11-15), zstd <i>is</i> pretty much Pareto optimal at all settings when looking at size vs. <i>decompression</i> speed. On the other hand at intermediate settings zstd is faster and produces smaller files than gzip, which therefore is <i>not</i> Pareto optimal (anymore).</p>
]]></description><pubDate>Sun, 15 Mar 2026 07:24:37 +0000</pubDate><link>https://news.ycombinator.com/item?id=47385063</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47385063</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47385063</guid></item><item><title><![CDATA[New comment by bonzini in "RISC-V Is Sloooow"]]></title><description><![CDATA[
<p>I think they have already added hardware page table walks.<p><a href="https://lwn.net/Articles/932048/" rel="nofollow">https://lwn.net/Articles/932048/</a></p>
]]></description><pubDate>Wed, 11 Mar 2026 07:28:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=47332605</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47332605</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47332605</guid></item><item><title><![CDATA[New comment by bonzini in "RISC-V Is Sloooow"]]></title><description><![CDATA[
<p>LoongArch is, on a first approximation, an almost RISC-V user space instruction set together with MIPS-like privileged instructions and registers.</p>
]]></description><pubDate>Tue, 10 Mar 2026 21:47:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=47329188</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47329188</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47329188</guid></item><item><title><![CDATA[New comment by bonzini in "JSLinux Now Supports x86_64"]]></title><description><![CDATA[
<p>Wow, with AVX512 too?? Now I really want to add it to QEMU. :)<p>(For APX I have patches at <a href="https://lore.kernel.org/qemu-devel/20260301144218.458140-1-pbonzini@redhat.com/T/" rel="nofollow">https://lore.kernel.org/qemu-devel/20260301144218.458140-1-p...</a> but I have never tested them on system emulation).</p>
]]></description><pubDate>Tue, 10 Mar 2026 10:29:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=47321382</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47321382</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47321382</guid></item><item><title><![CDATA[New comment by bonzini in "Mondrian Entered the Public Domain. The Estate Disagrees"]]></title><description><![CDATA[
<p>The article is about the Mondrian estate picking and choosing between the 95 year, life+70, and life+80 rules—and being wrong in all three cases.<p>So I wasn't doing a legal analysis of which rule is the correct one, but rather observing how their arguments are ridiculous.</p>
]]></description><pubDate>Tue, 03 Mar 2026 06:10:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=47228744</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47228744</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47228744</guid></item><item><title><![CDATA[New comment by bonzini in "Mondrian Entered the Public Domain. The Estate Disagrees"]]></title><description><![CDATA[
<p>I read "The duration of the U.S. protection for all other works… was for 70 years from the artist’s date of death" and thought wow, did Mondrian really live into the 1960s or so?<p>Next paragraph: "Mondrian died in 1944. Any of his works subject to a life-plus-70 regime would have entered the public domain" 10 years ago. Who even thought of including that in a legal argument??</p>
]]></description><pubDate>Mon, 02 Mar 2026 11:35:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=47216648</link><dc:creator>bonzini</dc:creator><comments>https://news.ycombinator.com/item?id=47216648</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47216648</guid></item></channel></rss>