<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: ku5h</title><link>https://news.ycombinator.com/user?id=ku5h</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 15 May 2026 17:16:16 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=ku5h" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by ku5h in "Rewrite Bun in Rust has been merged"]]></title><description><![CDATA[
<p>Because in the software world, especially before 2022, ownership and stability have been valued. People like using things that do not randomly start breaking more often after every new release, and if things break, there is a human who knows exactly why it broke and what's the best way to fix it. Businesses would not want their losses to be attributed to an AI rewriting an entire codebase. AI owns nothing, not even the bugs which it produces. I would not want my SaaS to have downtime because a JavaScript runtime it depends on decided that they had to market their LLM by rewriting years of code recklessly.<p>People are not betrayed by a rewrite. They are betrayed by an LLM rewriting with minimal supervision fasttracked to a merge within 9 days of commencement.<p>To the contrary I do not understand how we have become so insensitive towards stability since the LLM era. Why is unbreakable code no longer the goal but a truckload of generated code is.</p>
]]></description><pubDate>Fri, 15 May 2026 07:34:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=48145637</link><dc:creator>ku5h</dc:creator><comments>https://news.ycombinator.com/item?id=48145637</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48145637</guid></item><item><title><![CDATA[Ask HN: How to distinguish between concurrent, parallel, sync and async]]></title><description><![CDATA[
<p>I have seen all four terms used interchangeably. I know this sounds repeated, but I want a little more specific answer. I have already done my research. I found quite satisfactory results[0] explaining what each term meant. But what is still not clear to me, is how exactly would we differentiate them if we had to represent them through a Venn diagram.<p>My current understanding is the following -<p>1. All parallel things are concurrent, but all concurrent things are not parallel.<p>2. No synchronous things are asynchronous, and vice-versa.<p>3. Some synchronous things are concurrent, and some synchronous things are parallel.<p>4. All asynchronous things are concurrent, but only some asynchronous things are parallel.<p>https://i.imgur.com/fVK22xv.png<p>My question is whether my current understanding of the difference is correct. If not, how must they be categorized and why?<p>[0]: I watched Rob Pike's video on Concurrency is not Parallelism - https://www.youtube.com/watch?v=oV9rvDllKEg. And the following response on Reddit explaining the difference between synchronous and asynchronous code - https://www.reddit.com/r/computerscience/comments/ow1336/comment/h7d1h9d/ I have tried to summarize my findings in a blog post if you're willing to go through it - https://www.kush.in/post/a-sink-and-a-weight_1</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=40088506">https://news.ycombinator.com/item?id=40088506</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 19 Apr 2024 16:04:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=40088506</link><dc:creator>ku5h</dc:creator><comments>https://news.ycombinator.com/item?id=40088506</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=40088506</guid></item></channel></rss>