3 ms·
I went the other direction, I programmed for decades without syntax highlighting because back in 1989 I thought ANSI color directory listings were for MS-DOS we
by lamontcg 11y ago
I went the other direction, I programmed for decades without syntax highlighting because back in 1989 I thought ANSI color directory listings were for MS-DOS weenies, so I used a monochrome terminal for everything. I finally became a software developer and adopted syntax highlighting and haven't looked back. Catching unterminated strings and mismatched do..end blocks in ruby saves an incredible amount of time where you can just fix it immediately in-editor as you are coding.
I find it amusing that now we've got hipster programmers wanting to get back to basics and reject syntax highlighting. Trust me, its not better, colors do make you more efficient.
- noir_lord 11y agoI tried it with and without recently, I found that for languages I'm familiar with having it on or off made no difference however having flag errors on off did. For languages I don't use much I found having it on more helpful, could I work without it of course, I grew up with computers that didn't have syntax highlighting but I'd miss it. One side result of the experiment was that I turned down the number of colours I used, not everything needs to be a different colour.
- mst 11y agoThe only synhi I've ever not actively hated was the elvis defaults on a slackware install ten years ago, which basically bolded/italiced/faded text but didn't change the colour.
- mst 11y agoTypical mind fallacy. I've tried both and am vastly more productive with it off. Other people haved tried both and are vastly more productive with it on. I do often encourage people to try whichever one they're not currently using for a month as an experiment to see if they want to switch - calling people hipsters for performing an experiment to try and make themselves a better programmer strikes me as rather depressing.
- y4mi 11y agoyou're talking about a different aspect though. he says that you're more productive if you're writing a lot of code at one time. you're saying that its easier to catch minor syntax errors with syntax highlighting. this could, technically, be combined. i.e. writing code without syntax highlighting and enabling it for a quick glance to catch these errors that get obvious with the highlighting.