|
Article Publishing
|
~ the old camelcase problem |
One way to reduce the annoyance of typing CamelCase is to use thisStyle instead. Then you have one less obnoxious capital to type. But it is aesthetically not so pleasing to riddle your code with thisStyle of proceduresEverywhere. I just find ThisStyle to be more pleasing ...
The most tempting style of programming seems to be lisp-style-that does not require any-of-the-above and uses dashes. The issues is postfix/prefix notation and the minus sign being used now in procedure/function names.
I'm really just tired of the whole camelCase/CamelCase blues. It makes my fingers massively sore to type out all these pinky shift key straining capitals. Then you have the lower case underscore C style code like_this_which still requires a shift key.
No matter which way you take, it always has a disadvantage, except maybe the Lisp route, but it even has the disadvantage of using up the minus sign, depending on whether your language is postfix/prefix notation. And Lisp has the issue of bindings. When you bind a lisp function from a C library, of course all the underscores or CamelCase has to be converted to dashed-names.
Is it just a rumor or a joke that people have been hospitalized for typing on keyboards? Every time I program I dread that I'll have carpal tunnel or destroy my fingers eventually.
But what is really ticking me off is that in GoLang right now, I'm just finding that thisStyle() of function is not so aesthetically pleasing for local functions and the PublicFunctions with full camel case and not partial camel case, just look better than localFunctions().
|
|