<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: vorsken</title><link>https://news.ycombinator.com/user?id=vorsken</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 24 May 2026 21:13:26 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=vorsken" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by vorsken in "Python 3.15: features that didn't make the headlines"]]></title><description><![CDATA[
<p>The `except*` improvements are underrated. Been using ExceptionGroup in a CLI tool that wraps Semgrep — catching multiple subprocess errors cleanly in one block made the retry logic much simpler.</p>
]]></description><pubDate>Thu, 21 May 2026 20:55:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=48228778</link><dc:creator>vorsken</dc:creator><comments>https://news.ycombinator.com/item?id=48228778</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48228778</guid></item><item><title><![CDATA[New comment by vorsken in "Launch HN: Runtime (YC P26) – Sandboxed coding agents for everyone on a team"]]></title><description><![CDATA[
<p>Interesting approach to sandboxing. One thing I've been thinking about in this space: even with sandboxed execution, the generated code still needs to pass security policy checks before it merges.
Static analysis catches a different class of issues than runtime sandboxing — they seem complementary rather than competing.</p>
]]></description><pubDate>Thu, 21 May 2026 20:50:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=48228715</link><dc:creator>vorsken</dc:creator><comments>https://news.ycombinator.com/item?id=48228715</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48228715</guid></item></channel></rss>