<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Implementation of the Programming Language Dino -- A Case Study in Dynamic Language Performance · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1604.01290/</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/1604.01290/feed.xml" rel="self" type="application/rss+xml" /><item><title>Implementation of the Programming Language Dino -- A Case Study in Dynamic Language Performance — mentioned by jashmatthews</title><link>https://news.ycombinator.com/item?id=17226720</link><guid isPermaLink="false">urn:hackerpapers:mention:1604.01290:17226720</guid><pubDate>Mon, 04 Jun 2018 11:23:52 GMT</pubDate><description>&lt;p&gt;This is simply not true. You&amp;#x27;re massively underestimating the overhead of a bytecode VM. Even the most optimal bytecode VMs are easily beaten by the simplest of JITs in 100 lines of C: https://arxiv.org/pdf/1604.01290.pdf Code doesn&amp;#x27;t even need to be &amp;quot;hot&amp;quot; to make it worth it. WebKit switches from interpreter to cheap baseline compilation, without an specular optimizations or type information, after only 6 calls of a function: https://webkit.org/blog/3362/introducing-the-webkit-ftl-jit/ This article literally describes how baseline JIT is worth it simply to remove the bytecode VM dispatch…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1604.01290/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
