Isn't it simply a case of 'buggy syntax highlighting is useless'? In that case, 'syntax highlighting' becomes the least relevant part of the statement, compared to being the primary subject in the original version.
As for linter-during-typing, that only applies if you see syntax highlighting as a typing aid, which is arguably the least common usage.
In the linked blog post, the example of syntax highlighting applied to fiction is just a bad example because it's bad syntax highlighting regardless of whether the reader approves of syntax highlighting.
I agree with you about the weakness of the examples. Coming up with good examples is hard.
Isn't it simply a case if 'buggy syntax highlighting is useless'?
I'm not sure. Maybe they are downsides we don't even think about because we're so used to it.
if you see syntax highlighting as a typing aid, which is arguably the least common usage.
Then, what is it? Is is just for readability? If so, is a well-written code with no colors more readable than badly written code with excellent coloring?
I completely agree. But without appropriate examples, it's all just voicing of opinions without evidence or argumentation.
Maybe they are downsides we don't even think about because we're so used to it.
The only one dowside I've heard of that makes the least bit of sense is that you get used to it and therefore would have trouble if you didn't have it anymore. But the same is true for mostly everything, and it's also highly hypothetical (for most developers at least).
Then, what is it? Is is just for readability? If so, is a well-written code with no colors more readable than badly written code with excellent coloring?
Like the bad example in the linked blog post, this is also an unfair comparison: I'd rather have well-written code. Period. That's a matter that's entirely orthogonal to whether syntax highlighting has
value.
Also, the point of well-written code compared to poorly written code (assuming both of those do what they are supposed to), is exactly for readability, so 'just' doesn't really apply there.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Isn't it simply a case of 'buggy syntax highlighting is useless'? In that case, 'syntax highlighting' becomes the least relevant part of the statement, compared to being the primary subject in the original version.
As for linter-during-typing, that only applies if you see syntax highlighting as a typing aid, which is arguably the least common usage.
In the linked blog post, the example of syntax highlighting applied to fiction is just a bad example because it's bad syntax highlighting regardless of whether the reader approves of syntax highlighting.
I agree with you about the weakness of the examples. Coming up with good examples is hard.
I'm not sure. Maybe they are downsides we don't even think about because we're so used to it.
Then, what is it? Is is just for readability? If so, is a well-written code with no colors more readable than badly written code with excellent coloring?
I completely agree. But without appropriate examples, it's all just voicing of opinions without evidence or argumentation.
The only one dowside I've heard of that makes the least bit of sense is that you get used to it and therefore would have trouble if you didn't have it anymore. But the same is true for mostly everything, and it's also highly hypothetical (for most developers at least).
Like the bad example in the linked blog post, this is also an unfair comparison: I'd rather have well-written code. Period. That's a matter that's entirely orthogonal to whether syntax highlighting has
value.
Also, the point of well-written code compared to poorly written code (assuming both of those do what they are supposed to), is exactly for readability, so 'just' doesn't really apply there.