2,799 karma · joined March 9, 2012
That's the most reasonable way I am able to interpret what the original author was saying (tongue-in-cheek). Maybe it was a super petulant/arrogant/narrow way of viewing things but I prefer to give people the benefit of the doubt.
> I disagree that a piece of code ever becomes as familiar as an instrument. I've actually done both coding and music professionally. Once you learn an instrument you know it to the point you can close your eyes and play what you want. But I was very rarely reading the same code for very long periods, and as such I was always navigating new structures in a sense.
Keep in mind I happily use syntax highlighting myself (to the point of feeling crippled without it). I'm just trying to put myself in the shoes of someone who a) claims to not use it and b) sees it as "childish" (presumably because of being colorful and looking playful).
I've also played music (part-time professionally) and agree that it's not a direct comparison. But you're also kind of illustrating my point: With the instrument your mind creates a bunch of patterns (note placement and fingerings) to the point where you can play the instrument without the instrument, not only making color-coded keys/strings completely redundant after the initial familiarization process but even the whole visual experience! So without a doubt do colored piano keys look childish to a professional.
With coding you obviously cannot get rid of the need for visuals completely, but (I imagine) without syntax highlighting your brain is forced to use other methods of quickly identifying comments, functions, variables etc. Like ear training. If you use notation as a crutch to learn songs you won't develop the proper pattern recocnition required to identify notes/intervals/chords by ear. And while you're right that you're rarely looking at the same code for long periods of time, you're still looking at functions, objects, variables, constructors etc, like when learning music by ear. Maybe a better analogy would be using some kind of transcription software rather than your ears (with the argument that it's more precise than your ears etc etc). :D
I am not a neuroscientist so I cannot compare non-colored pattern recognition to the reading/grokking proficiency acquired through using syntax highlighting, but I'm doubtful that many people commenting on this topic are either. And thus I just wanted to bring forth an alternative viewpoint on this.
And for this being practicable, what I assume your main point is, the non-syntax-highlighting camp would only have a strong argument in favor of it if the end goal was to eventually work without it (like a pianist eventually not looking at the keys anymore). In that case it would (likely) act as a crutch, hindering the pattern recognition from forming. The scenario of not having syntax highlighting available only happens intermittently IRL, like sometimes being forced to use `less` to read code without syntax highlighting and feeling annoyed/crippled because your pattern recognition isn't trained to read it comfortably. For me it's a compromise I'm easily willing to make but I'm also not going to bash others for choosing a different path.
I now feel a bit tempted to try going without syntax highlighting for a couple of weeks and see how it goes. I used to do it all the time back in the day (BASIC, Turbo Pascal, batch scripts etc) but that was quite a while ago.
> Yes, that's exactly it. It's very rude to dismiss other people's needs as childish just because you don't share them. No one needs to discuss if highlighting is useful or not, we are all grownups capable of making that decision. I'm myself surprised that this needs to be pointed out
The responses I was reading was mostly people getting defensive very quickly, offended by how someone dares to claim that their method is not The Right Way™. I saw it (and still see it) in a way more light-hearted way of expressing the difference in approaches, rather than being dismissive. :shrug:
And just to counter your suggestion I often use `less` in environments where I am unable to install anything (or it doesn't make much sense to, like a Docker container).
You're trying to apply technical solutions to a problem where I was trying to highlight (pun intended) the cognitive function of a mind trained to read code without syntax highlighting vs one reliant on it (like my own). It doesn't matter if you can solve this particular one. Nor does it change the fact that someone who is used to seeing monochrome code might view colored code as playful and/or childish (like seeing colored piano keys).
tl;dr: A piano with colored keys (other than black/white) would "look childish". I don't even understand why this is a debate. It seems to be more about being offended by being called childish vs. thinking about what the actual issue is. And it's not even about being called childish, it's about someone who thinks syntax highlighting looks childish.
Edit: Also, traffic signs are colored to help you make quick decisions in an unfamiliar environment. A musical instrument isn't an unfamiliar environment for long. Nor is reading code.
Let me stop you there then: From that perspective viewing syntax highlighting as childish is normal for some brains. Empathy goes both ways.
> `less -R` preserves colours.
Preserves but doesn't magically add.
One clear example for me is that using `less` is always painful for me due to having used syntax highlighting as a crutch for so long. Those not using colored stuff will feel right at home with a wider range of tools. Just like people who don't use colored guitar strings can pick up any guitar.
If you're always using your own gear then there's not that much downside to customizing it. Unless those times where you need to use something else is of utter importance.
tl;dr: It definitely hurts something. Question is to which extent. Answer to that is probably that it depends.
I didn't use external monitors at home though (just laptop screen) - maybe that confuses things, if you have two separate external display setups?
> $23 a month, for a 48-month period with $2,900
2900/48 = ~60..?
Still, 60/month is very low. 43 mile range would be a dealbreaker for me though (not that you'd wanna venture very far at 28 mph).
Personally I'd be happy with a world with a lot less people, finding some sort of equilibrium. But it would necessitate a lot of pain to get there.
Agree with your point though.
Edit: It doesn't change the fact that the behavior is creepy though. Maybe that's the criticism.
To be clear I'm talking about Keyboard shortcuts -> Keyboard -> Move focus to next window.
[0] I was running Big Sur because none of the recent MacOS updates really offered anything of interest to me, since I don't use most Apple software. But Homebrew and Element stopped working so I had to upgrade. I should've just upgraded to a newer, not to the newest version (which I tend to avoid due to issues like these that might come up). Lesson learned.