zlacker

>>Bodaci+(OP)
I love how they name things

shouldSuppressAutocorrectionAndAutocaptializationInHiddenEditableAreasForHost(...)

>>l_f+ud
Can't leave any room for ambiguity!

Apple-style function/method naming may be verbose but at least the names usually have good explanatory value and aren't just meaningless verbosity.

>>kitsun+ag
And in the 21st century, everybody's using tab to autocomplete that string anyway.

>>shadow+5l
The problem is when you have multiple very long identifiers that differ only in a few characters. When scanning through code, it's much easier to see the difference between a saaainheafh and a saaainheafi than it is a shouldSuppressAutocorrectionAndAutocaptializationInHiddenEditableAreasForHost and a shouldSuppressAutocorrectionAndAutocaptializationInHiddenEditableAreasForInput.

Also, autocomplete doesn't work when you're reading and not writing, or just using a text editor or reading/annotating a printout (yes, I still do that.) IMHO writing code that almost completely relies on special tools to handle it is a bad trend.

>>userbi+un
This is a large open source project used by billions of people with many contributors. saaainheafh just doesn’t cut it.

>>peyton+6t
This weird abbreviation fetish was a big turnoff when I just got into programming (about 15 years ago when it was a lot more common). It’s just nonsensical and off putting.

>>grafta+zj1
You should try to change your perspective: Source code is its own language, and much like with natural languages, to get good at programming you should learn the language of the source code and not try to dumb-down by constantly trying to translate back to English.