new art: lapse

1 files changed, 27 insertions, 9 deletions

diff --git a/docs/posts/color_conundrum/index.html b/docs/posts/color_conundrum/index.html
index 6c493c2..eeba49b 100644
--- a/docs/posts/color_conundrum/index.html
+++ b/docs/posts/color_conundrum/index.html
@@ -33,7 +33,7 @@
               <span class="stats-unit">cm</span>
               &nbsp
               <span class="stats-number">
-                1.3
+                1.4
               </span>
               <span class="stats-unit">min</span>
             </div>
@@ -42,14 +42,32 @@
             Color Conundrum
           </h1>
           <div class="post-text">
-            <p>This piece aims to highlight (pun intended) some of the reasons behind my <a href="https://u.peppe.rs/bF.png">color free</a> editor setup.</p>
-<p>Imagine highlighting an entire book because <em>all</em> of it is important. That is exactly what (most) syntax highlighting does. It is difficult for the human eye to filter out noise in rainbow barf. Use color to draw attention, not diverge it.</p>
-<p>At the same time, a book devoid of color is <em>boring!</em> What is the takeaway from this 10 line paragraph? What are the technical terms used?</p>
-<p>Prose and code are certainly different, but the fickle minded human eye is the same. The eye constantly looks for a frame of reference, a focal point. It grows tired when it can’t find one.</p>
-<p>The following comparison does a better job of explaining (none, ample and over-the-top highlighting, from left to right):</p>
-<p><a href="https://u.peppe.rs/lt.png"><img src="https://u.peppe.rs/lt.png" /></a></p>
-<p>Without highlighting (far left), it is hard to differentiate between comments and code! The florid color scheme (far right) is no good either, it contains too many attention grabbers. The center sample is a healthy balance of both. Function calls and constants stand out, and repetitive keywords and other noise (<code>let</code>, <code>as</code>) are mildly dimmed out. Comments and non-code text (sign column, status text) are dimmed further.</p>
-<p>I’ll stop myself before I rant about color contrast and combinations.</p>
+            <p>This piece aims to highlight (pun intended) some of the reasons
+behind my <a href="https://u.peppe.rs/bF.png">color free</a> editor
+setup.</p>
+<p>Imagine highlighting an entire book because <em>all</em> of it is
+important. That is exactly what (most) syntax highlighting does. It is
+difficult for the human eye to filter out noise in rainbow barf. Use
+color to draw attention, not diverge it.</p>
+<p>At the same time, a book devoid of color is <em>boring!</em> What is
+the takeaway from this 10 line paragraph? What are the technical terms
+used?</p>
+<p>Prose and code are certainly different, but the fickle minded human
+eye is the same. The eye constantly looks for a frame of reference, a
+focal point. It grows tired when it can’t find one.</p>
+<p>The following comparison does a better job of explaining (none, ample
+and over-the-top highlighting, from left to right):</p>
+<p><a href="https://u.peppe.rs/lt.png"><img
+src="https://u.peppe.rs/lt.png" /></a></p>
+<p>Without highlighting (far left), it is hard to differentiate between
+comments and code! The florid color scheme (far right) is no good
+either, it contains too many attention grabbers. The center sample is a
+healthy balance of both. Function calls and constants stand out, and
+repetitive keywords and other noise (<code>let</code>, <code>as</code>)
+are mildly dimmed out. Comments and non-code text (sign column, status
+text) are dimmed further.</p>
+<p>I’ll stop myself before I rant about color contrast and
+combinations.</p>
 
           </div>