4 ms·
I started programming on VT-100s, moved to the IBM monochome (green) and then amber screens (over-hyped in my opinion.) Younger guys and their EVGA monitors wo
by baking 8y ago
I started programming on VT-100s, moved to the IBM monochome (green) and then amber screens (over-hyped in my opinion.) Younger guys and their EVGA monitors would program in yellow on magenta which I couldn't stand. But nothing is as bad for readability to my 60 year old eyes as all forms of gray on gray. Anyone trying to use a historical argument for this color scheme seems misguided to me.
- sureaboutthis 8y agoSame here. I do not understand the desire of these candy colors and what purpose they serve. Purportedly, it helps people find function or variable names but, in reality, it's just a blur of colors, each of which can mean multiple things. Give me white on black any day. I do like bold or gray on certain properties but only if it can be consistent and it's rarely consistent.
- kqr 8y agoI agree so much. I always have to create my own colour scheme for this reason. I want almost everything to be white on black, or black on white, and then I have like three exceptions to that: - source code comments are a slightly more dim gray and literal strings are a slightly more dim green, because they're characters that can look like code, but generally have no semantic meaning to the program; - structural keywords are an orangeish-brown to highlight the syntactical structure of the code; and - types belong to a different world than the syntax tree, so they are a contrasting blue. That's it. I don't want any more than that.