people who capitalise the first letter of a variable or method

File: 1474206708934.png (4KB, 558x565px) Image search: [Google]

4KB, 558x565px

People who use naming conventions other than sensible deviation from the language's norms are likely autistic.

>>57753581
Java """programmer""" detected

>>57753581
what about

my_variable = SomeFunction();

Shut The Fuck Up Dude You Don't Know Anything About Me Or The Struggles I've Had To Endure

>>57753581
>people who capitalise the first letter of a variable or method can into proper touch typing unlike you plebs

why is thisKindOfNaming preffered to this_kind_of_naming? It's much easier to read two-word variables since the _ is kind of a space?

>>57753917
>It's much easier to read two-word variables since the _ is kind of a space?
I don't follow that logic. Space suggests those are separate words. So unless your font size is autismal small, thisKindOfName should be easier to read.

The only thing that sucks is that acronyms are harder to spot as part of the word.

>>57753917
I only use an underscore to denote a GLOBAL_CONSTANT

>>57753960
but "image location" for example IS two words?
i feel imageLocation is too compressed. syntax highlightning should make it no problem

>>57753917

It's easier to write camelcase than snake case.snake case also takes up more space

>>57754026
>but "image location" for example IS two words?
But not in the parsers semantics, which is more important than the faggot natural language semantics in this scenario.

Pretending I'm not completely autismo natural language should be closer to my brain and therefore autocompleted easier than the programming languages parser semantics.

Dumb frogposter.

>>57753917

ruby fag deteced

>>57753581
>All go programmers can't be trusted

I'm okay with this

>>57754089
dumbFrogposter

ftfy

>>57753917
No way dude. my_cool_variable is easier.

Worst I've seen is faggots do objMyVariable or say intMyNumber in python.