What do you use and where?For me it's:>PascalCaseClasses, interfaces, types, objects and structs>camelCasefunctions, local / member variables>snake_caseGlobal variables / environment variables>UPPER_CASEConstants>kebab-caseKeys, files and directories
Snake case everywhere is obviously the correct choice. We figured out as English speakers that spaces between words is more readable than scriptio continua by the middle ages.
>>108607633class some_class {};Anon, Please tell me you don't do this
I have embraced Go's formatting style even in other languages.Pascal for public symbols, camel for private. And all the bracing rules and shit too.Anything non-code like directories etc. use full proper English. Programmers who do not account for whitespace or non-ASCII can die.
A thread died for this.
Whatever this ishttps://github.com/id-Software/Quake/blob/master/WinQuake/cmd.c#L614
>>108607534I like to switch it up from time to time or from file to file depending on what I feel like. Not letting some autists on the internet limit my creativity.
>>108607534Whichever style the project is currently usingIdeally, it should follow the language's preferred styling guide
>>108607534>kebab - case + sauces + hiv - whiteshuh?
>>108607534whatever is the default of the language I'm using
>>108607680> I have embraced Go's formatting style even in other languages. Pascal for public symbols, camel for private.Same. I used to have Go style, but now actually prefer it. I write D and use this convention there. Would still use snake_case in Ruby though because it's a strong convention.> Anything non-code like directories etc. use full proper English. Programmers who do not account for whitespace or non-ASCII can die.fuck you if you want me to always type quotes in paths just because you decided it's okay to have spaces in directory names because you never used terminal in your entire life and write code in VSCode like a total codemonkey. I would literally fire your ass the moment I saw this shit.
>>108607534What is the shit URLs use with + for spaces?
>>108607534Whatever AI gives me. Im not a codetrans luddite
>>108607534I don't use snake_case or UPPER_CASE anywhere in programming.
>>108607534the ultimate nodev thread
>>108608842>you never used terminal in your entire lifeI practically live in my terminal. I also live in 2026 and use a shell that has tab completion that inserts quotes automatically. I think this has been the case since the 80s.
>>108607534Hungarian Notation (Systems) is the one and only right one.
>>108607534It depends on the language I'm using. I generally prefer camelCase and PascalCase for most things, and reserve snake_case/UPPER_CASE for special symbols like constants.
>>108608842just use a backslash dude
>>108607534I use whatever is common at my current workplace and don't really care that much. I have one large personal open source project that is entirely Hungarian notation because that's what my work at the time did. My current personal project is a decomp/port project in which there were original engineers that used camel case, snake case, pascal case, and that one motherfucker who just tries to use as few characters as possible. So I just don't give a shit what the other contributors use.
functionname, variablenameCONSTANTNAMETypeName
PublicMethods()StructOrClassprivateMethod()local_variableCONSTANTregardless of the language, unless that language has very very strong bias (like Ruby naming methods in snake_case)I probably annoyed everyone with this, but this is very sane if you think about it. People who name their variables in camelCase don't understand ergonomics and that it's important to be able to quickly scan code visually without reading it.
>>108607534>snake_caseeverything but>PascalCaseTypes>Snaked_Pascal_Caseconstantsthat's it
>>108607534Pascal case for types, camel case for everything else.
>>108607633Unironically this
depends on what i'm usingalthough i do like kebab case for folder names regardless of language
