5 ms·
just-testing-this JustTestingThis Hmm. I think it only matters to me that the author picks one and stays with it. But that means that all libraries he uses ha
by easytiger 14y ago
just-testing-this
JustTestingThis
Hmm. I think it only matters to me that the author picks one and stays with it. But that means that all libraries he uses has to use the same one. Which is why languages tend to prefer one over the other. e.g. Java using CaMeLcAsE
To have them mixed in one code base would be like a micro context switch.
- deleted 14y ago[deleted]
- epo 14y agoI think most people have enough processing bandwidth to cope with external libraries using a different convention to inhouse code.
- robomartin 14y agoAh, see, you would have received an error when running this code! It's "justTestingThis" not "JustTestingThis" if we are talking camel case. So yeah, camel case and case sensitivity add unnecessary fragility to programming. Which is the reason I don't like the fad. You accidentally made my case.
- ramblerman 14y agoSorry to be pedantic but these are wrong examples: just-testing-this ---> just_testing_this JustTestingThis ---> justTestingThis The second one is less dramatic but the first one would in most languages subtract testing and this from just.
- easytiger 14y agoisn't justTestingThis a variable name and JustTestingThis a class/struct name?