From 5924e263893ac8c47a22a78c88b46c585fc9e82b Mon Sep 17 00:00:00 2001 From: Akshay Date: Sat, 25 Jan 2020 23:14:36 +0530 Subject: update styles, minify links --- docs/posts/color_conundrum.html | 64 ----------------------------------------- 1 file changed, 64 deletions(-) delete mode 100644 docs/posts/color_conundrum.html (limited to 'docs/posts/color_conundrum.html') diff --git a/docs/posts/color_conundrum.html b/docs/posts/color_conundrum.html deleted file mode 100644 index 113fd25..0000000 --- a/docs/posts/color_conundrum.html +++ /dev/null @@ -1,64 +0,0 @@ - - - - - - - - - - - - - -
-
-
31/12 2019
- - Color Conundrum - -
-

This piece aims to highlight (pun intended) some of the -reasons behind my color -free 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

- -

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.

- -
- ← Back -
-
-
- - -- cgit v1.2.3