<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: erupti</title><link>https://news.ycombinator.com/user?id=erupti</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 19 Aug 2026 18:25:01 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=erupti" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by erupti in "GPU Offload in Rust: Portable, Safe, and Fast"]]></title><description><![CDATA[
<p>> I think that will depend on the exact reason(s) C++ with LLVM offload didn't work out?<p>Are you making a claim or asking a question? ESL?</p>
]]></description><pubDate>Tue, 18 Aug 2026 07:14:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=49342422</link><dc:creator>erupti</dc:creator><comments>https://news.ycombinator.com/item?id=49342422</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49342422</guid></item><item><title><![CDATA[New comment by erupti in "GPU Offload in Rust: Portable, Safe, and Fast"]]></title><description><![CDATA[
<p>Unfortunately, the Rust description itself is inconsistent. It claims to be "sufficiently fast by default", yet "sufficiently fast" depends entirely on the requirements of a specific user project. And then it also plans to provide options that do not guarantee memory safety when the default speed is insufficient. It is already common for Rust projects to sprinkle memory unsafe code around when performance is needed.</p>
]]></description><pubDate>Tue, 18 Aug 2026 07:11:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=49342384</link><dc:creator>erupti</dc:creator><comments>https://news.ycombinator.com/item?id=49342384</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49342384</guid></item></channel></rss>