<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: cklee</title><link>https://news.ycombinator.com/user?id=cklee</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 28 Jul 2026 21:54:33 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=cklee" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by cklee in "Show HN: PgQueuer – Transform PostgreSQL into a Job Queue"]]></title><description><![CDATA[
<p>I’ve been thinking about the potential for PostgreSQL-backed job queue libraries to share a common schema. For instance, I’m a big fan of Oban in Elixir: <a href="https://github.com/sorentwo/oban">https://github.com/sorentwo/oban</a><p>Given that there are many Sidekiq-compatible libraries across various languages, it might be beneficial to have a similar approach for PostgreSQL-based job queues. This could allow for job processing in different languages while maintaining compatibility.<p>Alternatively, we could consider developing a core job queue library in Rust, with language-specific bindings. This would provide a robust, cross-language solution while leveraging the performance and safety benefits of Rust.</p>
]]></description><pubDate>Sun, 18 Aug 2024 20:26:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=41285205</link><dc:creator>cklee</dc:creator><comments>https://news.ycombinator.com/item?id=41285205</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41285205</guid></item><item><title><![CDATA[New comment by cklee in "Programming language comparison by reimplementing the same transit data app"]]></title><description><![CDATA[
<p>I posted to the Elixir Forum<p><a href="https://elixirforum.com/t/an-informal-comparison-of-several-programming-languages/51285" rel="nofollow">https://elixirforum.com/t/an-informal-comparison-of-several-...</a><p>----<p>It's not surprising that Elixir is not good at large json handling and complicated data structure manipulation. This reminds me of <a href="https://discord.com/blog/using-rust-to-scale-elixir-for-11-million-concurrent-users" rel="nofollow">https://discord.com/blog/using-rust-to-scale-elixir-for-11-m...</a><p>At the same time I see that Elixir gave the most consistent response time. Max response time is less than 6x of median compared to ~x10 (Deno / C#) or x23 (Go / Rust) / x58 (Scala), probably thanks to preemtive scheduling of per-request process in Erlang VM</p>
]]></description><pubDate>Mon, 24 Oct 2022 04:59:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=33313089</link><dc:creator>cklee</dc:creator><comments>https://news.ycombinator.com/item?id=33313089</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=33313089</guid></item></channel></rss>