<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: grepzero</title><link>https://news.ycombinator.com/user?id=grepzero</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 25 Jun 2026 03:00:52 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=grepzero" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by grepzero in "RubyLLM: A Ruby framework for all major AI providers"]]></title><description><![CDATA[
<p>The hard part with these unified wrappers is always the leaky bits: prompt caching, tool-use schemas, structured output, and reasoning tokens differ enough across providers that a common interface tends to quietly drop whatever's provider-specific. How does RubyLLM handle that, escape hatches down to the raw provider, or normalize to a shared subset? Prompt caching is the one I'd care
about most, since it's modeled pretty differently between OpenAI and Anthropic and
it's where most of my cost savings come from.</p>
]]></description><pubDate>Wed, 24 Jun 2026 22:37:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=48666411</link><dc:creator>grepzero</dc:creator><comments>https://news.ycombinator.com/item?id=48666411</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48666411</guid></item></channel></rss>