FaggotCase vs lowercase_underscores

If you aren't using lowercase_underscores (or lowercase-hyphens for you schemers) you're doing it completely wrong. PascalCase/camelCase aka JewCase identifiers take between 0.5-1.0 seconds longer to visually parse and identify.

http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=5521745&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5521745
http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=5970159&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D5970159
http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=5970176&navigation=1
http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6240505&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6240505
http://whathecode.wordpress.com/2013/02/16/camelcase-vs-underscores-revisited/
https://whathecode.wordpress.com/2011/02/10/camelcase-vs-underscores-scientific-showdown/

but TL;DR
lowercase_underscores : http://www.youtube.com/watch?v=_jXKIy_2p5U
NiggerCase : http://www.youtube.com/watch?v=0itOCgJtNVU

Thank you for the sources, I will use this to fuck with the code monkeys and corner rounders.

Results indicate that camel casing leads to higher accuracy among all subjects regardless of training, and those trained in camel casing are able to recognize identifiers in the camel case style faster than identifiers in the underscore style.
Results

    Camel casing has a larger probability of correctness than underscores. (odds are 51.5% higher)
    On average, camel case took 0.42 seconds longer, which is 13.5% longer.
    Training has no statistically significant impact on how style influences correctness.
    Those with more training were quicker on identifiers in the camel case style.
    Training in one style, negatively impacts the find time for other styles.

 Conclusion:CamelCase is superior is all aspects.

>>3
Fuck off yid.

On average, camel case took 0.42 seconds longer, which is 13.5% longer.
And those were with developers trained in using camel case. Still slower at identifying identifiers.

Multiple studies elsewhere found that the correctness difference is non-existent, especially when developers are trained in lowercase_underscores.

>>1
They have names:
https://en.wikipedia.org/wiki/Camelcase
https://en.wikipedia.org/wiki/snake_case

>>3
I was going to say this: [requesting source]
But I found your source:
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.158.9499&rep=rep1&type=pdf
7 Summary and Future Challenges
The study described in this paper shows that although
those without training take longer to recognize identifiers in
the camel case style, all subjects are more accurate when
identifying a camel-cased identifier. In addition, subjects
trained to use camel casing take less time to identify a
camel-cased identifier than an underscore identifier.
The next step is to consider higher-level tasks in more
realistic settings. One task would investigate the impact
of camel casing versus underscores when reading blocks
of code. For example, subjects might be asked to search
for a particular identifier. Another task would ask subjects
to read natural language para
graphs modified to use camel
casing or underscores. This would enable more direct com-
parisons with previous work done in psychology such as
Epelboim et al. [6].

IOW: Biased as fuck. Even "5.4 Threats to validity" section proof the point. My personal style is always the COBOL_WITH_UNDERSCORE_CONVENTION, making VARIABLES incredibly unambiguous as to what a var SHOULD = as. functions_left_to_reader(), however ᴛʜɪꜱ_ɪꜱ_ꜰɪɴᴇ_ᴛᴏᴏ().

FUNCTIONS_SHOULD_NOT_BE(int like_this, char* at_all);
it_just_looks_wrong(int SINCE_THE_VARIABLES, char* HAVE_GREATER_IMPORTANCE);
SeeIfICare(int ThatYouCanRead, char* ThisAtAll);
ItJustMakeIt(int confusing_as_hell, char* when_you_change_conventions);
data_has_higher_value(int ThanTheProcedures, char* ThatCallThem);

>>5 thats the source:
https://whathecode.wordpress.com/2011/02/10/camelcase-vs-underscores-scientific-showdown/ (from last line of OP post)
It quote the original paper

Camel4Lyfe
UnderscoreIsLoser

>>5
snake_case
is the one true casing style for /prog/, except when writing Scheme.  My other car is a cdr.

>>7
Your post is hard to read.

>>6
When reading the abstract of the research paper, it seems science is on the camel case side.
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.158.9499
http://www.cs.loyola.edu/~binkley/papers/icpc09-clouds.pdf

SAME MOTHERFUCKING SOURCE. READ THE RESEARCH TO SEE IT IS TOTALLY BIASED.  The control group does nothing, just nothing. 135 participants? Like that is demographic. If I recall, for an experiment to be representative, does it not need to have 1000 participants with at the least 5% statistical error?

I even provided you with a block experiment for you to use, to see if you what you can read easier, something that is not in the study. You are welcome to create your own miniature experiments with your colleges if you like.

By the way, here is a more carefully constructed one:
http://www.cs.kent.edu/~jmaletic/papers/ICPC2010-CamelCaseUnderScoreClouds.pdf
VIII. CONCLUSIONS AND FUTURE WORK
An eye-tracking study analyzing the effect of identifier style (camel-case and underscore) on accuracy, time, and visual effort is presented with respect to the task of recognizing a correct identifier, given a phrase. Visual effort is determined using six measures based on eye gaze data namely: fixation counts and durations. Although, no difference was found between identifier styles with respect to accuracy, results indicate a significant improvement in time and lower visual effort with the underscore style. The interaction of Experience with Style indicates that novices benefit twice as much with respect to time, with the underscore style. This implies that with experience or training, the performance difference between styles is reduced. These results add to the findings of Binkley et al.’s study [4]. Future work includes conducting more eye-tracking studies (with a larger subset of identifiers and larger subject sample), on reading source code consisting of both identifier styles, in the context of a specific task such as debugging. Another possible direction is to determine if there is an advantage for a programmer to change their current style to what is determined to be a better overall style.

>>3
FUCK YOU KIKE

Thread reported.

mup mup mup