shittyCase

Why did people even consider using this shitty unreadable method of separating words inside compound identifiers?  Why the fuck is it recommended style for Javascript, Haskell and other half-decent languages?  Why does Python use it in some of its identifiers (but not in all, because it is inconsistent shit)? 

Why won't underscores do (or even real spaces for some languages)?  Makes code much more readable.

>>8)0 ethn wnhy are y;qu uisng the sihfgh\t key at eall+/?
fukcn wokr eman, woh needxs to workb when youo have weeed

>>80
skipping vowels is jewish. don't do it

>>67
So very true.  As best I can tell, ACPI is really industry doublespeak for ``can run Windows''.

>>83
|ACPI is really industry doublespeak for ``can run Windows''
jesus christ are you mentally retarded or what

|
back to /b/, please.

thisIsTheWorstShit holy fuck

What amazes me is that fucking years after PEP-8 was published and widely accepted there are people who go on creating projects where all methods areCalledLikeThis as if they were still writing their familiar java/c# turdshit.  It's been 11 FUCKING YEARS, would it fucking murder these twisted, tornado, unittest etc guys to fucking adhere to it?  I couldn't give an infinitely small amount of fuck about their language background and that they are used to it, this is just fucking infuriating.

Twisted naming convention is a fucking mess
The Protocol class used throughout this document is a base implementation of IProtocol used in most Twisted
applications for convenience. To learn about the complete IProtocol interface, see the API documentation for
IProtocol.
Who the fuck calls classes IProtocol?  It's fucking PYTHON you fucking moron, there are no interfaces here!!!