1 files changed, 36 insertions, 0 deletions

diff --git a/posts/color_conundrum.md b/posts/color_conundrum.md
new file mode 100644
index 0000000..0e938b7
--- /dev/null
+++ b/posts/color_conundrum.md
@@ -0,0 +1,36 @@
+This piece aims to highlight (pun intended) some of the
+reasons behind my [color
+free](https://files.nerdypepper.tech/bF.png) editor setup.
+
+Imagine highlighting an entire book because *all* 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.
+
+At the same time, a book devoid of color is *boring!*. What
+is the takeaway from this 10 line paragraph? What are the
+technical terms used?
+
+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.
+
+The following comparison does a better job of explaining
+(none, ample and over-the-top highlighting, from left to
+right):
+
+![hi.png](https://files.nerdypepper.tech/lt.png)
+
+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 (`let`, `as`) are mildly dimmed
+out. Comments and non-code text (sign column, status text)
+are dimmed further.
+
+I'll stop myself before I rant about color contrast and
+combinations.