aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--posts/color_conundrum.md36
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 @@
1This piece aims to highlight (pun intended) some of the
2reasons behind my [color
3free](https://files.nerdypepper.tech/bF.png) editor setup.
4
5Imagine highlighting an entire book because *all* of it is
6important. That is exactly what (most) syntax highlighting
7does. It is difficult for the human eye to filter out noise
8in rainbow barf. Use color to draw attention, not diverge
9it.
10
11At the same time, a book devoid of color is *boring!*. What
12is the takeaway from this 10 line paragraph? What are the
13technical terms used?
14
15Prose and code are certainly different, but the fickle
16minded human eye is the same. The eye constantly looks for a
17frame of reference, a focal point. It grows tired when it
18can't find one.
19
20The following comparison does a better job of explaining
21(none, ample and over-the-top highlighting, from left to
22right):
23
24![hi.png](https://files.nerdypepper.tech/lt.png)
25
26Without highlighting (far left), it is hard to differentiate
27between comments and code! The florid color scheme (far
28right) is no good either, it contains too many attention
29grabbers. The center sample is a healthy balance of both.
30Function calls and constants stand out, and repetitive
31keywords and other noise (`let`, `as`) are mildly dimmed
32out. Comments and non-code text (sign column, status text)
33are dimmed further.
34
35I'll stop myself before I rant about color contrast and
36combinations.