The release of BritCSS, a tool designed to convert CSS properties to British English spellings, has ignited a fascinating debate about language evolution and standardization in programming. While the tool aims to allow developers to use traditional British spellings like background-colour instead of background-color, it has sparked discussions about the historical development of English spelling and the implications of introducing dialect variations into programming languages.
Existing CSS Spelling Accommodations:
- grey/gray: Both spellings accepted
- color: Standard CSS property
- colour: Proposed alternative by BritCSS
Implementation Methods:
- Client-side JavaScript
- Supports inline styles
- Supports CSS files
- Supports HTML style tags
Historical Context Challenges Tool's Premise
Community members have brought forward compelling historical evidence that challenges the tool's fundamental assumption about bastardised spellings. Linguistic experts in the discussion point out that many American spellings actually preserve older forms of English, with the colour spelling being a later addition influenced by French. The evolution of English spelling reveals a complex history where what's considered correct has shifted numerous times over centuries.
Spelling is always an entirely cultural artefact, and that before colour was spelt color, it was spelt colos. There's nothing more correct about older forms, or newer forms, or any other forms. What matters is what is going to be clearest to your speech community and audience.
Technical and Practical Concerns
Several developers have raised practical concerns about introducing dialect variations into programming languages. The introduction of alternative spellings could potentially fragment code bases, making it more difficult to share code across projects and reducing the effectiveness of documentation and Stack Overflow solutions. Additionally, the implementation as a JavaScript preprocessor has raised concerns about potential vulnerabilities and maintenance overhead.
Standardization in Programming Languages
The discussion has highlighted interesting parallels with existing inconsistencies in web technologies. The HTTP Referer header's notorious misspelling and its later correction in Referrer-Policy serves as a cautionary tale about the importance of standardization in programming languages, regardless of regional spelling preferences. CSS already accommodates some spelling variations, such as grey and gray, showing there's precedent for flexibility in certain cases.
The debate surrounding BritCSS ultimately reflects broader questions about balancing cultural heritage with practical standardization in programming languages. While preserving language diversity is valuable, the programming community appears to favor maintaining consistent standards that facilitate global collaboration and code sharing.
Reference: BritCSS: Fixes CSS to use non-bastardised spellings