<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Encoder-Decoder Gemma: Improving the Quality-Efficiency Trade-Off via Adaptation · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2504.06225/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2504.06225/feed.xml" rel="self" type="application/rss+xml" /><item><title>Encoder-Decoder Gemma: Improving the Quality-Efficiency Trade-Off via Adaptation — mentioned by luke-stanley</title><link>https://news.ycombinator.com/item?id=45974363</link><guid isPermaLink="false">urn:hackerpapers:mention:2504.06225:45974363</guid><pubDate>Wed, 19 Nov 2025 00:43:29 GMT</pubDate><description>&lt;p&gt;Simon, sorry I didn&amp;#x27;t get around to answering your question on post-t5 encoder-decoders from the Markdown Lethal Trifecta prompt injection post. (https://news.ycombinator.com/item?id=45724941) Since the plain decoder models stole the show, Google DeepMind demonstrated a way to adapt LLMs,adding a T5 encoder to an existing normal Gemma model to get the benefits of the more grounded text-to-text tasks WITHOUT instruction tuning (and the increased risk of prompt injection). They also have a few different kinds they shared on HuggingFace. I didn&amp;#x27;t get around to fine-tuning the weights of one for…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2504.06225/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
