deploy: 9c092a1

Author: nbriggs

project/index.html

@@ -220,7 +220,7 @@ <h1>The Medley Interlisp Project</h1>
 	</header>
 	<h1 id="reviving-a-groundbreaking-system">Reviving a Groundbreaking System</h1>
 <h2 id="what-are-we-trying-to-accomplish">What are we trying to accomplish?</h2>
-<p>Our aim is to allow Medley to &ldquo;live again&rdquo;: to be useable enough on modern systema that someone could develop some code and experience what it was like to use this groundbreaking system. You could think of this as a kind of &ldquo;<em>vintage software</em>&rdquo; project, to try to capture the sense of fluidity in the development cycle.</p>
+<p>Our aim is to allow Medley to &ldquo;live again&rdquo;: to be useable enough on modern systems that someone could develop some code and experience what it was like to use this groundbreaking system. You could think of this as a kind of &ldquo;<em>vintage software</em>&rdquo; project, to try to capture the sense of fluidity in the development cycle.</p>
 <p>We also hope to provide a platform for revival of systems developed using Interlisp., including 1980&rsquo;s work in hypertext (Notecards), desktop management (Rooms), and object-oriented programming (LOOPS).</p>
 <p>The lessons from the Interlisp interactive environment is likely more relevant in today&rsquo;s &ldquo;devops&rdquo; environment &ndash; managing large networks of independent microservices, with no single serialization of the components quite comprehensible. Development in this model has been called &ldquo;repl-driven development&rdquo;: you are working in the &rsquo;live&rsquo; environment (or a copy) making changes without a separate, lengthy edit-compile-load-restart.</p>
 <h2 id="what-are-our-challenges">What are our challenges?</h2>