<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: throw74838484</title><link>https://news.ycombinator.com/user?id=throw74838484</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 11 Jul 2026 20:53:21 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=throw74838484" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by throw74838484 in "Girls just wanna have fast MPMC queues with bounded waiting"]]></title><description><![CDATA[
<p>Because it would not even pass initial code review for most developers. Most people use short review prompt, with yes/no answers.<p>Imagine the code compilers (or some analysis tool) gives several concurrency and memory warnings. It has easy workaround (just annotate strange code, with links to explanations that this is workaround for low level bugs).<p>I am too tired of shitty "safe" Rust code, with 'unsafe' section around every library call (not case here, just an example)! Be clear with that, it takes 15 minutes and 10 cents!<p>This project could have correct concurrent code and design, but around much narrower definitions. But most people will not go too deep with review to find it!</p>
]]></description><pubDate>Thu, 09 Jul 2026 19:55:03 +0000</pubDate><link>https://news.ycombinator.com/item?id=48851563</link><dc:creator>throw74838484</dc:creator><comments>https://news.ycombinator.com/item?id=48851563</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48851563</guid></item></channel></rss>