British English vs. American English

[Supermichael777]

The fighting about which form of English is proper or common or should be the standard or utter lack of a standard is beginning to generate CODE DRAMA that threatens FEATURES. As this is a BAD THING, we should have some sort of vote or discussion not on #coderbus which, while an excellent platform for conversation is a poor choice for discussions that get this heated. Coder internal policy is a bit opaque and everyone is on or off or idle at different time,s and with such a location dependent issue different opinion groups rarely get on at the same time which leads to the debate shitting up pull requests. We should have a vote or something somewhere. So color or colour?

THE OPTIONS

• BRITISH ENGLISH
• AMERICAN ENGLISH
• WHATEVER THE FUCK THE ORIGINAL CODER OF THE VAR WANTED TO USE
• WHATEVER THE FUCK THE LAST GUY TO FIND/REPLACE WANTED TO USE (current)

[Wyzack]

Holy fuck you people will cry about anything

[onleavedontatme]

I switch between the two at random you can't stop me

[TehSteveo]

I switch between the two at random you can't stop me

You mad man!

[Saegrimr]

I honestly really don't care which, but having a colour and a color var doing different things on the same item would be pretty fucking dumb.

[onleavedontatme]

I honestly really don't care which, but having a colour and a color var doing different things on the same item would be pretty fucking dumb.

I laughed when I saw a line of code where armor checked for armour_penetration

[Not-Dorsidarf]

Its getting to the point where we might as well use the german for every cross-language instance of different spellings.

[TheNightingale]

That could work. Or "colo(u)r"? Do brackets mess up code?

[Jordie0608]

So long as you use spelling consistent with the existing file it doesn't actually matter which you choose.

[DemonFiren]

Its getting to the point where we might as well use the german for every cross-language instance of different spellings.

I'll be here as translator if you need me and don't want to incur the wrath of someone who will rigorously correct every instance of mistranslated variables.

[Incoming]

Using color over colour technically reduces the file size of the project.

[oranges]

Australian English

[Saegrimr]

Using color over colour technically reduces the file size of the project.

This is the best argument i've heard from either side.

[Remie Richards]

Using color over colour technically reduces the file size of the project.

if we wanted to reduce filesize we'd use relative pathing.
We're not switching to relative pathing any time soon, and if we ever do, it would be for the compilation time benefit, not the filesize one.
tl;dr that's not even a valid argument.

[asskek]

Using color over colour technically reduces the file size of the project.

if we wanted to reduce filesize we'd use relative pathing.
We're not switching to relative pathing any time soon, and if we ever do, it would be for the compilation time benefit, not the filesize one.
tl;dr that's not even a valid argument.

it was a joke dweeblord

and it still does reduce filesize

[Steelpoint]

Ah yes, my 500kb file will be reduced to a 498kb thanks to these cost cutting measures.

[iamgoofball]

I saw one of our contributors saying that we've dealt with mismatching english standardization for 5 years and that it's a "non-issue". (Before you claim this is starting drama, I'm not naming names and just using this to point out a problem we have as a whole)

If we're going to call ourselves a professional project, then we need to fucking standardize instead of acting like whiny retarded 5 year olds and shitting ourselves over a single fucking letter every goddamn 5 months or so.

The solution to this is for us to DO SOMETHING.

You know how we have that PR tester system because of shit like steelpoint's gun PR? And how we were able to run it on the server without merging it (but then someone merged it anyways for ??? reasons)? This was because I took action, told cheridan and mso to play 7 minutes in heaven in an irc channel and build a pr tester system.

We can fix these problems. We just need to stop shitting around and DO SOMETHING.

I'm going to run a search of the code base tomorrow and see how many instances of "color" and "colour" I pick up. I'm going to use these to determine which we'll be using as a standard.

If you want to reply to this post to tell me why this is bad and to not do it, I want 5 good reasons to not do it.

If your list includes "it works the way it is" the existence of this thread and the fact that every time a PR shows up involving the word color/colour a shitstorm happens in the comments over it being spelled "right" or "wrong" proves that your reason is false.

[oranges]

go away goof, it's not worth the shitstorm it causes.

>professional project

just stop with the memes please.

[oranges]

This whole argument saps my will to live, just stop caring about it when people make pr's, dont' make a stupid pr changing 5000 files just to change one var and everythign will be fine.

[oranges]

ps it's standardise

[imblyings]

i always thought it was standardize

[NikNakFlak]

i always thought it was standardize

[Saegrimr]

I thought it was standaroo over in those parts

[Remie Richards]

I don't assume it was malicious since it is that person's first PR

That was a joke, he has 78 (rough number from github search) PRs on tgstation, it's fucking xxalpha, he's NOT new.

[Malkevin]

[TheNightingale]

I think the question we need to ask ourselves is not "Is it colour or color?", but "Is it worth correcting the colors to colours?".

[oranges]

i always thought it was standardize

i always thought it was standardize

Thanks for finishing my punchline twice

[Scott]

That was a joke, he has 78 (rough number from github search) PRs on tgstation, it's fucking xxalpha, he's NOT new.

Oh, in that case then he should bloody well know to keep controversial things away from other things.

Death to those who spell things wrong!

It's not controversial to me, man.

[NikNakFlak]

That PR really wasn't a big deal. Xxalpha added a new var that was spelled the american way "color" and it was right below an existing var that was spelled "colour" so he changed the old var to match the new var. Remie then had an aneurysm because he changed the old brit var to match the american var instead of making the new var match the british var. It's a maintainer pushing for british stuff too.

[asskek]

the brits can't even maintain Big Ben

why are they maintaining our code

[Remie Richards]

Biased Butthurt Admin

[asskek]

Biased Butthurt Admin

how is he biased

or at least any more biased than you

this entire argument is built on bias

bias isn't necessarily bad or a killer of logic

[Remie Richards]

Biased Butthurt Admin

how is he biased

or at least any more biased than you
this entire argument is built on bias
bias isn't necessarily bad

He's been Buttblasted with me for about a month now.
For one of his OWN fuckups.

He even abused his admin rank to get me banned for a day, but it got removed because again, it was just him abusing his rank.

[NikNakFlak]

Not relevant and bringing up past offenses doesn't change the argument or any of the points in it really

[Saegrimr]

this entire argument is built on bias

Pretty much this.

There is zero way to solve this that doesn't end in some sort of bias.
1: Whoever wants muh spelling more
2: Goof's proposal that we just switch to whichever brings more results in a search. "b-but muh american/british coders shitting up the repository by spamming the wrong spelling everywhere! Unfair! Bias!"
3: Incoming's suggestion which actually has a mechanical advantage over the other, even if it results in less than a kilobyte of data reduced it's still the only actual unbiased mechanical advantage here.

The asspain flows both ways, Remie.

[asskek]

I've only seen a couple people try to compromise on this and they've both been ignored

maybe we should listen to them

edit: removed my response to remie because their post's been deleted

[asskek]

I think the question we need to ask ourselves is not "Is it colour or color?", but "Is it worth correcting the colors to colours?".

by "compromise" I mean what this guy is saying

or incoming's entirely logical proposal

or goof's seemingly fair idea

[Remie Richards]

Alright, fuck you lot then.

[oranges]

That PR really wasn't a big deal. Xxalpha added a new var that was spelled the american way "color" and it was right below an existing var that was spelled "colour" so he changed the old var to match the new var. Remie then had an aneurysm because he changed the old brit var to match the american var instead of making the new var match the british var. It's a maintainer pushing for british stuff too.

I think you should be deadminned for intentionally misgendering someone

[Remie Richards]

That PR really wasn't a big deal. Xxalpha added a new var that was spelled the american way "color" and it was right below an existing var that was spelled "colour" so he changed the old var to match the new var. Remie then had an aneurysm because he changed the old brit var to match the american var instead of making the new var match the british var. It's a maintainer pushing for british stuff too.

I think you should be deadminned for intentionally misgendering someone

He's actually talking about xxalpha in that last bit.

[NikNakFlak]

I thought that was apparent because xxalpha was doing the var changing in that story yea.

[oranges]

Okay I misread that sorry

[Malkevin]

I'll just say that the international coding standard used in everything from HTML to C++ is to use American English.

Not because its the right way or anything, but because its best to keep things simple for the septics.

[asskek]

I'll just say that the international coding standard used in everything from HTML to C++ is to use American English.

Not because its the right way or anything, but because its best to keep things simple for the septics.

things are looking in favor of american english now
two entirely objective points in its favor:
1. It's the standard for other languages
2. It drops the file size by 1/32 of a kilobyte.

[asskek]

Then go make a PR removing all u's and changing every ess to a zed.

You have the power asskek, you are the chosen one.

doing it now

just have to reinstall byond and get started

get ready for the fattening

[invisty]

Talk about a storm in a teacup.

[Not-Dorsidarf]

It is now official we will be replacing all instances of color and colour with Farbe

[Saegrimr]

It is now official we will be replacing all instances of color and colour with Farbe

What about the plural?

[DemonFiren]

Well, technically you should be using "Farbton", as that means the shade as opposed to something that could also be taken (and mostly is) to mean "paint".
Plural would be Farbtöne, if you don't into umlaut use (oe) for (ö).

Told ya ya'd need me.

[Fayrik]

Told ya ya'd need me.

DemonFiren for /tg/ official variable namer.
All new variables must be named, signed and approved by DemonFiren.

Seriously though, how about not changing other people's variable names to reflect your own culture?
If Remie had done this, the entire PR would have been closed with comments like

Fuck England trying to invade again muh freedom guns woo fuck england

Well it works both ways.
Fuck America, fuck the illusion of freedom, fuck guns, you get the picture.
Color or colour, whatever. Just stop the fucking one-upmanship.

Talk about a storm in a teacup.

That's racist.

Spoiler:

I was going to continue my rant but then I saw this and fucking lol'd.