<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scaling Laws with Vocabulary: Larger Models Deserve Larger Vocabularies · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2407.13623/</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/2407.13623/feed.xml" rel="self" type="application/rss+xml" /><item><title>Scaling Laws with Vocabulary: Larger Models Deserve Larger Vocabularies — mentioned by freeqaz</title><link>https://news.ycombinator.com/item?id=45643568</link><guid isPermaLink="false">urn:hackerpapers:mention:2407.13623:45643568</guid><pubDate>Mon, 20 Oct 2025 13:18:49 GMT</pubDate><description>&lt;p&gt;There is also a tradeoff between different vocabulary sizes (how many entries exist in the token -&amp;gt; embedding lookup table) that inform the current shape of tokenizers and LLMs. (Below is my semi-armchair stance, but you can read more in depth here[0][1].) If you tokenized at the character level (&amp;#x27;a&amp;#x27; -&amp;gt; embedding) then your vocabulary size would be small, but you&amp;#x27;d have more tokens required to represent most content. (And context scales non-linearly, iirc, like n^3) This would also be a bit more &amp;#x27;fuzzy&amp;#x27; in terms of teaching the LLM to understand what a specific token should &amp;#x27;mean&amp;#x27;. The letter…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2407.13623/"&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>
