<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: erupti2</title><link>https://news.ycombinator.com/user?id=erupti2</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 19 Aug 2026 19:10:19 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=erupti2" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by erupti2 in "GPU Offload in Rust: Portable, Safe, and Fast"]]></title><description><![CDATA[
<p>But it still depends on the requirements of the specific user project, whether the default is sufficiently fast, ESL. It is still entirely inconsistent. Basic logic 101, clear as day. Why do you even try to contest this?<p>> It's a mirror of Rust's general design goals, if anything.<p>Do you claim that "it's a mirror of Rust's general design goals, if anything" to be forced into memory unsafe, extra-difficult Rust code being required, when the going already gets tough regarding performance requirements? That is not a great design goal, and it is not conducive to memory safety nor high quality software.</p>
]]></description><pubDate>Tue, 18 Aug 2026 13:42:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=49345524</link><dc:creator>erupti2</dc:creator><comments>https://news.ycombinator.com/item?id=49345524</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49345524</guid></item></channel></rss>