this post was submitted on 19 Oct 2025
32 points (61.6% liked)
Programming
23348 readers
290 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Very strong opinions for something entirely subjective and endlessly configurable.
I failed the question about remembering what colour my class definitions were, but you know what? I don't care. All I want is for it to be visually distinct when I'm trying to parse a block of code
yeah, this guy got syntax highlighting backwards. It never occurred to me that I should know the element-to-color mappings of my theme. For what good would that serve?
Between multiple IDEs, text editors, diff viewers and editors, and hosted tools like MR/review diff, they're not even consistently just one thing. For me, very practically and factually. Colors differ.
As you point out, they're entirely missing the point. What the colors are for and how they're being used.
Yeah, if I want to know what the colour is to find other instances of that thing easier, it takes 2 seconds to determine the colour. But I can't remember ever actually doing that.
That retunr typo will be caught by the compiler. That's what pass 1 is pretty much for, spell and syntax check.
I care about knowing what which color means ostensibly (not sure how much it actually benefits me,) but I also actually do, for the vscode default theme.