Hardly alone. I use no color except for comments and errors.
Rob Pike has no color - he thinks it is juvenile.
https://groups.google.com/g/golang-nuts/c/hJHCAaiL0so/m/kG3B...
I just don’t see the utility in having a bunch of colors.
Rob Pike has no color - he thinks it is juvenile.
https://groups.google.com/g/golang-nuts/c/hJHCAaiL0so/m/kG3B...
I just don’t see the utility in having a bunch of colors.
totally and absolutely bonkers.
colour is insanely helpful as a _sense_ that can aid our brains in parsing. we aren’t compilers; it’s fine to like colour and not like colour but to say there can be no benefit or, worse, that it’s juvenile is even more childish of a statement.
eh, one thing i’ve learned is smart people in one field are not universally smart, and that’s ok.
In all seriousness, it's a valid opinion. All the best programmers I know had relatively bare bones setups. I've found when I get in the habit of using IDEs are things like ChatGPT, I start to get sloppy. If the language server or whatever is tracking the logic of the code to tell you whether it will parse correctly, then you aren't using your brain as much to do it.
Syntax highlighting adds more visual information to the code to help your brain navigating it. Some people probably don't need it, but personally it helps me tremendously and I would have to have to program without it. It's like eye shortcuts.
While color for syntax highlighting is relatively new, it does date to the 1980's, , and so if it was a person it'd be middle aged by now...
Even long before that the syntactic conventions of many languages were designed to achieve much the same (e.g. different casing patterns), some of which have survived into modern languages, along with a long string of "pretty printing" tools that to format things with bold, underline, italics etc.
The only reason I didn't rely on color for highlighting much in the early 90's was that e.g. at university I often still worked on monochrome terminals.
Bet. No true adult likes colors.
i switched from VSCode to CLion (for Rust) the other night and only lasted 5 minutes because i missed how alternating braces change color.
For me it's searchable local history and searchable recent locations- both jetbrains features that vscode falls flat on.
Native stack-based clipboard is up there, but there is a vscode plugin.
With those three features I can do what I think of as "fearless development" where I can just delete / change things without a second thought, easily able to undo/find old changes without needing to micro manage.