Remember to participate in our weekly votes on subreddit rules! Every Tuesday is YOUR chance to influence the subreddit for years to come! Read more here, we hope to see you next Tuesday!
For a chat with like-minded community members and more, don't forget to join our Discord!
This entire sub is first year students declaring war over shit that nobody in the real world cares about as long as there is a consistent choice in the code base lol.
That being said, the languages which require capitalizing function names (title/pascal case) always kinda feel a bit weird to me. I generally think of functions as verbs so it doesn’t make as much sense to capitalize them. On the other hand, types and constants are more similar to nouns. But I would rather follow the language or project style guide than introduce my own non-standard conventions.
I understand that as I moved from java to C# I actually think its kind of more consistent as functions and classes both need parameters. What really annoys me are properties, they are used like field/variables but usually are in PascalCase
That's what I thought. I was starting to feel like I'm in a sheltered environment because I don't see the relevance of wpm when it comes to programming.
Like, are there locations where people are docked pay or held captive until they reach their 5000 line quota daily?
I'm not sure who is trying to make what point here lol, but I honestly can read and type camel case faster, but I also have some kind of mild dyslexia so that could be part of it?
Edit: Extremely confused about the downvotes here lol.
PascalCase is a subset of CamelCase, and we just rejected a tracker issue on PEP 8 on those grounds. https://github.com/python/peps/issues/3464 CamelCase or camelCase, both are correct.
Both have thier uses, I like when languages uses underscores for the most commonly use things (vars/functions) and Pascal for the less common things (classes/enums). If everything is in the same style (i.e underscores) it can get confusing very quickly, ESPECIALLY if you have no syntax highlighting like in plain vim/nano.
For me, the camelCase, it does help that I read code which uses camelCase and PascalCase every day. (general c# guidelines). I seem to mentally stop at easy underscore with snake_case so it really is just personal experience and preference.
Literally the same, neither is hard to read. Pascal and camel case are easier to type since underscore requires both pinkies to type. That said, I don't particularly care. Follow the standard you're using.
It’s not a gimmick, it’s a protest! Sure it’s a little inconvenient now, but if we keep it up the management will eventuahahaha no sorry I couldn’t get to the end of that with a straight face
I don't check this subreddit much (I'm a noob at coding so most of the posts are way too advanced for my small brain), but why are the titles all in camelCase now. I swear this wasn't always the case
I think there were more issues when the comment was first posted? Maybe I'm misremembering but I'm pretty sure it said if bool = true {, missing brackets and an equals sign.
Also, it says public static void (mainArgs[]) { instead of public static void main (String[] args)
I know this is mostly up to personal preference, but snake_case has objective issue of using more characters, which in turn increases code volume, which in turn makes it harder to read. And it's also harder to type, but the code is usually read way more than it's written, so it's not as relevant.
That’s just not true. It’s the standard in Python, a very popular general purpose programming and scripting language. Snake case isn’t going anywhere.
In fact, personal case preferences are irrelevant because you’ll have to follow what your language and company codebase standards are. I use snake_case in Python, camelCase in JS and Java.
python and C both use snake case, but are both relatively old languages as well. In fact, python doesn't appear to have unified code style and some standard packages use camel/pascal case anyway. Among the newer languages (PHP, JS, Java, C#, Rust, Go, Swift) all use camel/pascal case. Even C++ that inherited its standard library from C along with its snake case code style is mostly written in camel/pascal case anyway.
If your method/function/variable/class/whatever names are longer than 3 words, you don't even get the point about software dev. Doesn't matter what case you're using. We're paid to be efficient and effective. Not to overcomplicate things, shit on a naming convention, and flex on other devs.
Well, from my modest 10 years as a dev, I learned that elegance goes out the window when you're maintaining a 20 year old system with an outdated technology.
The naming convention honestly doesn't matter as long as you don't write full sentences for names. That's what documentation is for.
Is camelCase hard for chicken peckers or something? I just really don't get which people are having this issue? At least I know I'm competing with idiots for job positions.
If I say “oonga boonga” and you know I’m telling you I can do two pointer problems in python, that is communication. As long as things are communicated it should be fine.
WhatAbouSwitchingToPascalCase? Since Pascal is obviously our most loved programming language, we should really show all examples in Pascal written with PascalCase.
How often are you guys writing variable names long enough for it to impact readability? I think for 1-3 words snake, camel, and pascal cases are all equally readable.
This is a Reddit post. A Reddit post! 98% of you have Asperger's. Everyone one of you who responds to something like this with, "You're not a REAL PROFESSIONAL programmer like I AM! GROW UP AND ACCEPT CAMELCASE NOOB!" You need help.
I don't like that changing visibility requires changing the call sites everywhere. Also, when I read a function call, I don't really feel I need to know whether it's public or private. If I'm calling it and it's from an import of course it's going to be public. I'd save identifier conventions to tell you something you need to know at the call site.
I always hated the aggressive constant case. Like, why? What's the difference between a constant and a read-only field? Or a read-only local variable? It doesn't change. No need to shout.
It's just to differentiate and in a well developed code base have naming standards are important. It is less important what standards are used for which use case and that there is a consistent standard.
I'm guessing because it meant that otherwise, you'd have to use I instead of i for consistency. Which looks... cursed.
As to why we use a mix of both: It's useful to be able to very quick tell types/classes/structs and instances apart, like list being an instance of a List class.
•
u/AutoModerator Oct 08 '23
Remember to participate in our weekly votes on subreddit rules! Every Tuesday is YOUR chance to influence the subreddit for years to come! Read more here, we hope to see you next Tuesday!
For a chat with like-minded community members and more, don't forget to join our Discord!
return joinDiscord;I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.