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