Live data from Hacker News

BritCSS: Fixes CSS to use non-American English

github.com

61–70 of 180 posts

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

#61
post #18

Earlier quoted context omitted.

However, that is not the perspective of the creator of BritCSS, who refers to current CSS property names as "bastardised" spellings.

S/he's wrong, simple as that. "The particular spatio-temporal version of speech that I grew up with is correct, and all others are bastardised" is not a defensible or - frankly - interesting position. Chaucer would find virtually all modern English to be debased; Bede would wince at Chaucer's English; and so on, forever. Nothing fruitful comes from cultivating arrogance towards the language of others. It is just as m…

It's a joke.

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

#63

Earlier quoted context omitted.

I think it's a play on the Chinese language having Traditional/ Simplified versions. I'm choosing to take this repo as tongue-in-cheek, which is hard to really determine online...

I want to see it as tongue-in-cheek as well, but, I feel like that's a stretch...what would be the humor in that? But even if it doesn't make sense to me, I prefer your interpretation of motive.

Look as a Brit let me reassure that it is a joke. No one thinks American English is simpler than British English.

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

#65

Earlier quoted context omitted.

However, that is not the perspective of the creator of BritCSS, who refers to current CSS property names as "bastardised" spellings.

I mean, wouldn't the U.S as a nation essentially be a bastard child of Britain, and thusly use a bastardized English?

The colonies were acknowledged as the offspring of Britain .. the United States of America is more of a chosen fraternity of the emancipated offspring after they fled the control of their former legal guardians.

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

#66
post #18

Earlier quoted context omitted.

However, that is not the perspective of the creator of BritCSS, who refers to current CSS property names as "bastardised" spellings.

S/he's wrong, simple as that. "The particular spatio-temporal version of speech that I grew up with is correct, and all others are bastardised" is not a defensible or - frankly - interesting position. Chaucer would find virtually all modern English to be debased; Bede would wince at Chaucer's English; and so on, forever. Nothing fruitful comes from cultivating arrogance towards the language of others. It is just as m…

your wrong

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

#67
post #31

I believe that some people's actual full-time job is to translate software from US English to British English. I wonder what that job feels like after the thousandth time you've replaced color with colour and neighbor with neighbour

As a programmer working in the UK I've never been asked to rewrite something into British English. I have been instructed to convert some old codebase to American spellings to "avoid confusion". Probably about 6 times in 20 years of professional programming and usually by some product manager based in San José following an acquisition. This is why the library exists I expect.

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

#68
post #31

I believe that some people's actual full-time job is to translate software from US English to British English. I wonder what that job feels like after the thousandth time you've replaced color with colour and neighbor with neighbour

As a programmer working in the UK I've never been asked to rewrite something into British English. I have been instructed to convert some old codebase to American spellings to "avoid confusion". Probably about 6 times in 20 years of professional programming and usually by some product manager based in San José following an acquisition. This is why the library exists I expect.

To be clear, I don't think the library would actually be used to accomplish this task. Rather I suspect a tounge in cheek reaction to years of tedious spelling adjustment disguised as urgent feature requests.

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

#69
post #28

Why does the author use `initialize` for a function name in the source code? I question their purity of intentions!

Filthy non-OED user. The author is probably a Cambridge dictionary person!

Seriously, -ize endings in the Cambridge spelling tradition relies on you knowing the etymology of the word, and if it’s from the Ancient Greek, that’s the one you use. Otherwise -ise for French or Latin words.

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

#70

1. All of this could have been avoided but for the want of some MPs for some colonies. But no. 2. "License: Not Specified" instead of "Licence: Not Specified"

Speaking as a non-native English speaker, I'm not sure how I feel about American imperialism replacing British imperialism in general, but as far as English spelling and phonology goes, god bless America.
Post reply on HN