&gt; To provide an interpreter that can embed inside a Go application, in order to provide scriptability to the Go ecosystem at large.<p>Can we move away from scripting engines at some point. They are big black boxes that you throw characters into and then &quot;things&quot; happen that you have no control over.<p>* What if I <i>don&#x27;t</i> want the security?<p>* What if I want more security?<p>* What if I want actual pointers?<p>* What if I want to do one of a million things that don&#x27;t fall into the original assumptions about what a Go interpreter would do?<p>Compiler-as-a-service is the future. A high quality parse tree, with a built-in interpreter or possibly JITter. Refactoring tools and tons of other cool things can be built instead of the same old black box.<p>If it&#x27;s just going to be another plain-old interpreter, it would be best to instead focus on integrating V8 because a Go interpreter would bring far less to the table (notably interpreters are typically slow and one of the big benefits of Go is that it can be fast).