News for hackers. Stuff that matters.
Re:Bootstrap 2.3 Released by easytiger on Friday February 08, 2013 @03:07AM (#5186833)
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.

Re:Bootstrap 2.3 Released by robomartin on Friday February 08, 2013 @09:36AM (#5188028)
Ah, 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.

Re:Bootstrap 2.3 Released by josteink on Friday February 08, 2013 @11:17AM (#5188535)
camelCase vs PascalCasing is used to signal and separate public from private in C#, so that you always know what kind of data or function you are working with.

It's useful.

Re:Bootstrap 2.3 Released by Legion on Friday February 08, 2013 @12:34PM (#5189007)
Having a convention is useful. It doesn't necessarily have to be that particular one.
Re:Bootstrap 2.3 Released by ramblerman on Saturday February 09, 2013 @03:03AM (#5192060)
Sorry 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.

Re:Bootstrap 2.3 Released by easytiger on Sunday February 10, 2013 @03:21AM (#5195801)
isn't justTestingThis a variable name and JustTestingThis a class/struct name?
Re:Bootstrap 2.3 Released by epo on Friday February 08, 2013 @06:35AM (#5187319)
I think most people have enough processing bandwidth to cope with external libraries using a different convention to inhouse code.