Well... first of all, this is a well-known topic that widely discussed everywhere already.
- [1] https://www.robertmelton.com/project/syntax-highlighting-off/
- [2] https://dudzik.co/digress-into-development/syntax-off/
- [3] http://www.linusakesson.net/programming/syntaxhighlighting/
- [4] https://groups.google.com/forum/#!msg/golang-nuts/hJHCAaiL0so/kG3BHV6QFfIJ
- [5] http://howivim.com/2016/damian-conway/
- [6] https://twitter.com/enneff/status/710071512330477568
- [7] https://www.youtube.com/watch?feature=player_embedded&v=dkZFtimgAcM#t=15m58s
So I started turning off my Vim's syntax color from May this year, it's 5 months already.
There some real benefits for it that I can confirmed now:'
- Getting more focus on the work, that mean, more productivity
- Read/understand the code better, and even faster
- Vim run faster as well
-
Being way more cooler, my colleagues now look at me as a guy from Mars
Is there anyone doing the same thing?
P/S: This is the color scheme I'm using for my vim https://gist.github.com/huytd/8394f21bda3a08be025813c060d64e75
Latest comments (30)
We teach with a plain text editor at first - to show what that's like. No one chooses to keep using it after we show them sublime. We find syntax highlighting to be very helpful.
Your screenshot includes bold keywords and dimmed comments, so I assume you're either rolling your own or using a minimal syntax highlighting scheme, rather than actually turning it off?
You say "Getting more focus on the work, that mean, more productivity" but the only coloured thing on your screen, which immediately grabs attention, is a clock and a song title, both of which are totally unrelated to work (unless you're coding a bot that writes metal...)
First of all, it's a personal preference.
Whatever makes you more productive the better. Personally though, I'd prefer syntax highlighting over the other because unlike you, it allows me to read, understand and browse the code much faster.
Your vim setup looks amazing by the way!
I agree. It's just the matter of personal taste, and I tend to share my taste to find more people just like me (or hopefully convert someone's taste :P)
This is the color scheme I use. I am curious to try without colors, but I need to change all the entries in the preferences and right now I am lazy... Maybe I'll try.
Reflecting a bit, I think that the most important highlighting for me are the keywords and the comments. I could definitively do without highlighting for strings and numbers and maybe type names too.
How can you say:
Getting more focus on the work, that mean, more productivity
Read/understand the code better, and even faster
Without a parallel you working on the same thing over that period of time? This is bogus click bait.
Ha! I never noticed how little syntax highlighting I was actually using until I read this post and then quickly looked at my editor screen. Being colour blind means that I'm not seeing a lot of the "additional" information being added, so the end result is that I have 3 colours in use (base, constants, and strings) with bold for keywords.
I personally would think that too many colour variations would become distracting and slow down coding because you have to remember what each colour means rather than understanding the actual text of the code. But that's just me.
Do whatever makes you more productive. Working code is more useful than "pretty" non-working text :D
That kind of music will destroy your productivity anyway, j/k, I'm also a fan of Amon Amarth.
But I see the syntax highlighter will help me more productive, maybe it's everyone to his taste.
I'm trying this out. Also trying out VIM since I delayed it quite some time!
I'm curious about your status line style and that music playing thingy. Would you mind sharing it? I love the style of it :)
It's just a script to display current playing song on Spotify on Tmux status line. You can take a look at github.com/jdxcode/tmux-spotify-info
For the tmux, I made a config file public here gist.github.com/huytd/10e490955d34...
Actually I've thought about this before. When I do it I realize that it encourages me to add more whitespace around things. I actually have a color scheme right now that highlights mostly comments which encourages me to write better docs. I think that most color schemes are just too dumb and aren't telling you much about your code. Really folks, just try it for a day or two as an exercise, see if your code comes out better.
Haha, I can’t believe some of these responses... seriously people? I learned to code long before syntax highlighting was a thing, and honestly, while I do use it today, I like a very tame color scheme for the most part. To me it seems like everyone should basically create their own theme, because we all think differently, and we all react to colors and other distractions differently.
Anyway, here’s to experimentation and exploration!