Syntax highlighting is a waste of an information channel

Summary

The author argues that syntax highlighting is an underutilization of color as an information channel in code editors. They propose semantic highlighting as a more effective alternative, but acknowledge implementation challenges. The article explores various use cases for semantic highlighting and discusses the limitations of current editors.

Key Takeaways

1. Syntax highlighting is a waste of an information channel because color could be used to convey more meaningful information about code.
2. Semantic highlighting, which highlights code based on its meaning, could provide more valuable insights for developers.
3. Implementing semantic highlighting faces challenges such as accessing code's AST, handling highlighting conflicts, and editor limitations.

Statement Breakdown

• Claimed Facts: 50% of statements the article presents as facts
• Opinions: 30% of statements classified as editorial or subjective
• Claims: 20% of statements surfaced for additional reader evaluation

Credibility & Bias Reasoning

Credibility assessment: The article presents a well-reasoned argument against the overuse of syntax highlighting, supported by examples and potential use cases. The author acknowledges the challenges in implementing semantic highlighting, adding to the credibility. The article is published on the author's personal website, which could introduce some bias, but the arguments are logical and technically sound.

Bias assessment: Technological Improvement Advocacy. The author advocates for a shift from syntax highlighting to semantic highlighting, framing it as a necessary technological advancement. While the author presents a balanced view by acknowledging the challenges, the overall tone suggests a preference for semantic highlighting. This perspective is driven by a desire for improved coding tools and workflows.

Note: The article presents a reasoned argument, but readers should consider the author's perspective when evaluating the potential benefits and challenges of semantic highlighting.

Credibility flag: Thoughtful Critique

Claimed Facts (6)

• This is a generally accepted fact about human perception.
• Acknowledges the current utility of syntax highlighting.
• Describes the technical requirements for implementing semantic highlighting rules.
• Describes the technical implementation of syntax highlighting.
• Describes the current state of semantic highlighting in VSCode.
• Referring to rainbow parenthesis.

Opinions (5)

• This is the author's central argument and a subjective assessment.
• This is a subjective assessment of the importance of syntax highlighting.
• Expresses the author's preference for customizable highlighting rules.
• This is the author's assessment of the complexity of semantic highlighting.
• Expresses the author's belief in the future adoption of semantic highlighting.

Claims (5)

• While aliasing can be complex, claiming it's an 'open problem' without specific evidence is a dubious generalization.
• This is a vague prediction without specific justification.
• This is a speculative statement about where semantic highlighting might first appear.
• This is a generalization about the examples provided, which may not be entirely accurate or representative.
• This is a subjective metric for code quality, and its relevance to highlighting is questionable.

Key Sources

• Author — Computer Things