Show HN: GlyphLang – An AI-first programming language

1作者: goose000427 天前原帖
While working on a proof of concept project, I kept hitting Claude&#x27;s token limit 30-60 minutes into their 5-hour sessions. The accumulating context from the codebase was eating through tokens fast. So I built a language designed to be generated by AI rather than written by humans.<p>GlyphLang<p>GlyphLang replaces verbose keywords with symbols that tokenize more efficiently:<p><pre><code> # Python @app.route(&#x27;&#x2F;users&#x2F;&lt;id&gt;&#x27;) def get_user(id): user = db.query(&quot;SELECT * FROM users WHERE id = ?&quot;, id) return jsonify(user) # GlyphLang @ GET &#x2F;users&#x2F;:id { $ user = db.query(&quot;SELECT * FROM users WHERE id = ?&quot;, id) &gt; user } @ = route, $ = variable, &gt; = return. Initial benchmarks show ~45% fewer tokens than Python, ~63% fewer than Java. </code></pre> In practice, that means more logic fits in context, and sessions stretch longer before hitting limits. The AI maintains a broader view of your codebase throughout.<p>Before anyone asks: no, this isn&#x27;t APL with extra steps. APL, Perl, and Forth are symbol-heavy but optimized for mathematical notation, human terseness, or machine efficiency. GlyphLang is specifically optimized for how modern LLMs tokenize. It&#x27;s designed to be generated by AI and reviewed by humans, not the other way around. That said, it&#x27;s still readable enough to be written or tweaked if the occasion requires.<p>It&#x27;s still a work in progress, but it&#x27;s a usable language with a bytecode compiler, JIT, LSP, VS Code extension, PostgreSQL, WebSockets, async&#x2F;await, generics.<p>Docs: <a href="https:&#x2F;&#x2F;glyphlang.dev&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;glyphlang.dev&#x2F;docs</a><p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;GlyphLang&#x2F;GlyphLang" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;GlyphLang&#x2F;GlyphLang</a>
查看原文
While working on a proof of concept project, I kept hitting Claude&#x27;s token limit 30-60 minutes into their 5-hour sessions. The accumulating context from the codebase was eating through tokens fast. So I built a language designed to be generated by AI rather than written by humans.<p>GlyphLang<p>GlyphLang replaces verbose keywords with symbols that tokenize more efficiently:<p><pre><code> # Python @app.route(&#x27;&#x2F;users&#x2F;&lt;id&gt;&#x27;) def get_user(id): user = db.query(&quot;SELECT * FROM users WHERE id = ?&quot;, id) return jsonify(user) # GlyphLang @ GET &#x2F;users&#x2F;:id { $ user = db.query(&quot;SELECT * FROM users WHERE id = ?&quot;, id) &gt; user } @ = route, $ = variable, &gt; = return. Initial benchmarks show ~45% fewer tokens than Python, ~63% fewer than Java. </code></pre> In practice, that means more logic fits in context, and sessions stretch longer before hitting limits. The AI maintains a broader view of your codebase throughout.<p>Before anyone asks: no, this isn&#x27;t APL with extra steps. APL, Perl, and Forth are symbol-heavy but optimized for mathematical notation, human terseness, or machine efficiency. GlyphLang is specifically optimized for how modern LLMs tokenize. It&#x27;s designed to be generated by AI and reviewed by humans, not the other way around. That said, it&#x27;s still readable enough to be written or tweaked if the occasion requires.<p>It&#x27;s still a work in progress, but it&#x27;s a usable language with a bytecode compiler, JIT, LSP, VS Code extension, PostgreSQL, WebSockets, async&#x2F;await, generics.<p>Docs: <a href="https:&#x2F;&#x2F;glyphlang.dev&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;glyphlang.dev&#x2F;docs</a><p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;GlyphLang&#x2F;GlyphLang" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;GlyphLang&#x2F;GlyphLang</a>