<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: fancyraccoon</title><link>https://news.ycombinator.com/user?id=fancyraccoon</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 16 Apr 2026 19:23:20 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=fancyraccoon" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by fancyraccoon in "I still prefer MCP over skills"]]></title><description><![CDATA[
<p>Really interesting post. The "connectors vs manuals" framing stuck with me because I think it points at something beyond the UX argument. A Skill that papers over an API loses the signal the friction was carrying. Working with a raw interface tells you something about the design.<p>The same thing plays out at the language layer. The pain of C++ multiple inheritance drove people toward better abstractions. If LLM's absorb that friction before it reaches anyone, the signal that produces the next Go never gets felt by the people who could act on it.<p>Wrote about where that leads: <a href="https://blog.covet.digital/a/the_last_language_you_can_read.html" rel="nofollow">https://blog.covet.digital/a/the_last_language_you_can_read....</a></p>
]]></description><pubDate>Fri, 10 Apr 2026 11:47:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=47716667</link><dc:creator>fancyraccoon</dc:creator><comments>https://news.ycombinator.com/item?id=47716667</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47716667</guid></item></channel></rss>