FeralRobots , 3 months ago

@dalias I'm not sure that counts as 'incompatible.' It means that particular script doesn't have that nuance. But if we're talking language & not script, the terms are going to be translated anyway - so the original case is irrelevant.

As for aesthetics, I've never understood the argument against it.

dalias OP , 3 months ago

@FeralRobots No, I mean if you're trying to write identifiers in your own language that doesn't have case, then there is no way to write them in camelcase.

I'm talking about actual non-English/non-Latin source files, not translating identifier names into another language when talking about them.

FeralRobots , 3 months ago

@dalias In that case, one literally /can't/ write in camelcase, so I guess I'm not understanding how the issue comes up.

khm , 3 months ago

it comes up because the 'code style' police blindly enforce received wisdom instead of assessing the context of a given source file.

CC: @dalias

FeralRobots , 3 months ago

@khm @dalias
So teams where there are members typing in different scripts?

khm , 3 months ago

yes. there's a whole big world out there and sometimes we collaborate on stuff

CC: @dalias

FeralRobots , 3 months ago

@khm @dalias
You do realize a simple, non-sarcastic answer would have sufficed, right?

khm , 3 months ago

anything worth doing is worth doing well

CC: @dalias

FeralRobots , 3 months ago

@khm
where by 'well' you apparently mean 'dickishly.'

khm , 3 months ago

I'm not aware of any other definition of the word, and am unwilling to learn