massive CL is massive

src/site/articles/why-not-bytecode/index.html

 ---
 layout: default
 title: "Why Not a Bytecode VM?"
 rel:
   author: bob-nystrom
   author: florian-loitsch
 ---
 
 <section>
 <h1>Why Not a Bytecode VM?</h1>
@@ skipping 118 matching lines @@
 step" is just refreshing the browser. Dart must be equally simple to use.
 We want to make
 development in the browser a great experience. Not only do we want to keep the
 fast 'edit-refresh-view' cycle that JavaScript developers love, but
 we also want to introduce web developers to the powerful live editing
 features that Smalltalk developers pioneered.
 Sure, you may minify or do other obfuscation when you deploy, but your core
 iteration loop is fast and easy because the engine for your language runs it
 directly from source.</p>
 
-<aside class="note">You may ask, "but doesn't Dart require an explicit compile step to
+<p>
+  You may ask, "but doesn't Dart require an explicit compile step to
 compile to JavaScript for running in the browser?" Well, yes, but we're talking
 specifically about the native Dart VM here. And we <em>are</em> working to make
-the Dart-to-JavaScript side of things as nice of a development experience as we can. Iteration time matters.</aside>
+the Dart-to-JavaScript side of things as nice of a development experience as we can. Iteration time matters.
+</p>
 
 <h2>Compiling to source</h2>
 
 <p>Of course, Scala and <a href='http://research.microsoft.com/en-us/um/cambridge/projects/fsharp/'>F#</a> show that a new language can be developed
 for an existing VM, but it's possible to do that without bytecode: you can compile to source. Right now, if you want a new language that runs in the browser, compiling to JavaScript is your only option. <a href="http://jashkenas.github.com/coffee-script/">CoffeeScript</a> is the most prominent example of this today, but there are <a href="https://github.com/jashkenas/coffee-script/wiki/List-of-languages-that-compile-to-JavaScript">many others</a>. Dart itself compiles to JavaScript to let you use it on browsers that don't support Dart natively.</p>
 
 <p>Likewise, if you want a new language that runs on Dart's native VM, you could compile that language to Dart. Doing so will then let your language take advantage of all of the optimizations that the VM does when it compiles from source to machine code. In other words, Dart <em>is</em> your (highly specialized) bytecode.</p>
 
 </section>