Live data from Hacker News

BritCSS: Fixes CSS to use non-American English

github.com

1–10 of 180 posts

Re: BritCSS: Fixes CSS to use non-American English

#6
Obliged to point out that "color" is how it's spelled in Latin, Old French, and therefore post-Norman English, that the superfluous "u" was added later by the English aristocracy because they were jealous of how fancy the newly-respelled French looked.

Re: BritCSS: Fixes CSS to use non-American English

#7
post #6

Obliged to point out that "color" is how it's spelled in Latin, Old French, and therefore post-Norman English, that the superfluous "u" was added later by the English aristocracy because they were jealous of how fancy the newly-respelled French looked.

Obliged to point out that 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.

Re: BritCSS: Fixes CSS to use non-American English

#8
This creates a second language where two dialects that have minor differences meaning stackoverflow code won’t always work, nor will code you extract from other websites. This creates a mess, all while adding a JavaScript pre-processor that is prone to have errors, vulnerabilities and other flaws from the NPM hellscape. No thanks.

Re: BritCSS: Fixes CSS to use non-American English

#9

This creates a second language where two dialects that have minor differences meaning stackoverflow code won’t always work, nor will code you extract from other websites. This creates a mess, all while adding a JavaScript pre-processor that is prone to have errors, vulnerabilities and other flaws from the NPM hellscape. No thanks.

[deleted]

Re: BritCSS: Fixes CSS to use non-American English

#10

This creates a second language where two dialects that have minor differences meaning stackoverflow code won’t always work, nor will code you extract from other websites. This creates a mess, all while adding a JavaScript pre-processor that is prone to have errors, vulnerabilities and other flaws from the NPM hellscape. No thanks.

[deleted]
Post reply on HN