<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: scriptinglanguages</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/scriptinglanguages.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2008-06-08T09:36:47+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Joe Gregorio</title><link href="https://simonwillison.net/2008/Jun/8/joe/#atom-tag" rel="alternate"/><published>2008-06-08T09:36:47+00:00</published><updated>2008-06-08T09:36:47+00:00</updated><id>https://simonwillison.net/2008/Jun/8/joe/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://bitworking.org/news/321/The-Professionalization-of-Scripting-Languages"&gt;&lt;p&gt;There was a time when you could whip out a parser in lex and yacc, stitch together a naive VM and throw it over the wall and you'd have a new scripting language. Those days are coming to a close and in a few years (if not months) you won't be able get traction with anything unless it does direct threading, is register based, has generational GC, does peephole optimizations, does trace-folding, does type-inferenced inline caching, etc.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://bitworking.org/news/321/The-Professionalization-of-Scripting-Languages"&gt;Joe Gregorio&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/dynamic-languages"&gt;dynamic-languages&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/joe-gregorio"&gt;joe-gregorio&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scriptinglanguages"&gt;scriptinglanguages&lt;/a&gt;&lt;/p&gt;



</summary><category term="dynamic-languages"/><category term="joe-gregorio"/><category term="scriptinglanguages"/></entry></feed>