camelCase


    A variable in a programming language is sait to be camelCased when all
    words but the first are capitalized. This practice contrasts with the C
    tradition of either running syllables together or marking syllable breaks
    with underscores; thus, where a C programmer would write thisverylongname
    or this_very_long_name, the camelCased version would be thisVeryLongName.
    This practice is common in certain language communities (formerly Pascal;
    today Java and Visual Basic) and tends to be associated with
    object-oriented programming.

    Compare BiCapitalization; but where that practice is primarily associated
    with marketing, camelCasing is not aimed at impressing anybody, and hackers
    consider it respectable.

CamelCase

    The practice of concatenating words with either all
   words capitalised (e.g. "ICantReadThis" - sometimes called
   "UpperCamelCase" or "PascalCase") or all except the first
   ("iCantReadThis" - called "lowerCamelCase").  It is used in
   contexts where space characters are not allowed, such as
   identifiers in source code.

   Modern best practice separates words in identifiers with
   underscore for readability (like_this_example).  CamelCase is
   probably a historical throw-back to systems that had no underscore
   or when the length of identifiers was constrained either by the
   programming language or by the width of computer displays.
   Unfortunately it has infected many projects, origanisations and
   programming languages such as Java where the uniniated create
   identifiers like "MemberSubmissionAddressingWSDLParserExtension".

   (2014-12-02)