From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
It depends a bit on the use case. I try to follow naming conventions within specific environments like Python. When just sorting some documents together, I usually do a mix of Kebab and snake case, where I split semantic parts with underscores and connect words with dashes like
2024-08-30_author_document-name_other-important-info.ext
This is exactly what I do. It lends itself to something like 'prefix_specific-info_version' which is both sortable and easy to read.
Yeahh that's the best IMO ! But I get most of the time stuck with some testOFtest001 files/directory... cause I'm lazy...
But I always ALWAYS regret it afterward... :/
Snake case.
I put an unnecessary amount of spaces in all my file names to break anyone who wants to use CLI tools on them
i use windows btw
Using Windows is a true flex on Lemmy
I put newlines in my filenames to break both CLI tools and Windows filesystems
Underscore to delineate different parts, hypen to delineate words.
Like: my-resume_draft.pdf
And to make it consistent and easier to reuse parts for project names and such, I have a command line utility written for it. It caches the parts and uses a template system (support for generating current datetime in parts)
Available here (is in AUR too):
You can go-to_hell.
Thats what I do as well. It makes it easy to seperate between logical units.
SCREAMING_SNAKE_CASE just has the best name
YES, I USE THIS TOO TO STAY CONSISTENT WITH SQL QUERIES
I like Camel Case for code, but mostly because it's ingrained in my brain, coming from Java as my first language.
For folders and files, I like Kebab Case.
Luckily, I was not ingrained by my first programming language like that, or my coworkers would strangle me.
I started with BASIC, which allowed only two letters for variable names...
I am a fan of Python's or Rust's official conventions.
For package names, tho, I don't get why this-is-used over this_clearly_better_system, as I would expect a double click to select_the_whole_thing, whereas it does-not-happen-here.
For files, kebab case. For variables, snake case. For servers, megaman villains.
Camel case, but with a twist -- if the next word is about to start after a capital letter, I'll have it lower case.
topSecretFBIfile.txt for example
Interesting, I'd tend to demote the initialism, ie topSecretFbiFiles.tar.gz
I like to use my enterprise number and a UUID (all in lower case, for legibility). Here's an example:
.1.3.6.1.4.1.33230.0d456e46-67e6-11ef-9c92-7b175b3ab1f1
Now you might say that the UUID is already globally unique or at least pretty unlikely to turn up anywhere else, so why bother prefixing it with more stuff? To that I say: "I need to be absolutely or at least reasonably sure ... OK nearly sure".
Anyway, you maintain a database of these things and then attach documentation and meaning to them. An editor could abstract and hide that away.
I started this post as a joke. Not sure anymore. Why get your knickers in a twist with naming conventions for variables and constants. Programming is already a whopping layer of abstraction from what the logic gates are up to, another one wont hurt!
How about "cool file name"?
All my systems use modern file systems that are case sensitive and can contain any character except / and \0.
True. Linux, Android, Windows all have no problems
Using dots in a file though...
For files? An unholy amalgam of snake, kebab and dot, depending on what exactly I'm trying to convey. (I still have much-ported files around with DOS 8.3 filenames, so they're truncated scream case (SCREAMIN.NAM), but I don't actively name files like that anymore.) The important thing is to separate the words/sections while using characters that are valid without escapes in both ext4 and vfat if at all possible.
For variable names, camel or Pascal case (depending on language convention) if I think anyone else is going to read it. Flat case for code I don't think anyone else is ever going to see (don't do this—it has left teethmarks in my ass from time to time and will do the same to you).
WIAT, Y R U CALLIN IT SCREAMING CASE THAT SOUNDS FKN DUM TBH
L8R DOODZ
-SP4SEM4N B1FF
25% Camel case, 25% Pascal and 50% of the time flatcase. It drives me insane when I try and autocomplete a folder only to realise it was Downloads instead of downloads. I keep telling myself i will go through and make it all flatcase but I put it off because i tell myself i will rebuild my computer next week every week.
Never thought about making the home folders flatcase, thanks, takes all of 2 minutes btw.
If anybody else wants to do it, remember to edit ~/.config/user-dirs.dirs with your new flatcase folders.
The only correct answer is to be consistent with the code base you're working in or the language's conventions. If neither of these conventions exist, then someone has already failed you.
I’ve never been to a naming convention but I have been to some comic conventions!
Snake case. I find it the easiest to read.
I'm starting to warm up to Pokemon case, which would simplify functions like
GottaCatchThemAll() to 🍚()or
this to ⚡🐹IchooseUwhich I think we can all agree is much easier to read
Kebab or snake for ease of parsing through them.
Random mix and match. I’m all for diversity!
Depending on environment/language and policies. As long as its consistent throughout the project.
Unless I can't, Kebab.
No need to hold Shift.
Kebab. Not my favorite visually speaking but I had RSI issues for a while and I'm still very focused on limiting keystrokes (no shift key needed with kebab).
It really depends.
If I know I will never open the file in the terminal or batch process it in someways, I will name it using Common Case: "Cool Filename.odt".
Anything besides that, snake case. Preferably prefixed with current date: "20240901_cool_filename"
Rfc3339 plus kebab case for many things
2024-09-01_lname-fname-resume.pdf
Snake case, but I'm the World's second worst programmer and just name files like this because I was alive when spaces were not allowed.
I've got a personal convention that file names get snake case, directory names get Pascal case.
It heavily depends on the context: Filenames? Variables? Functions? Interfaces/Classes? Java? C? Shell?
Depends. Java-like languages ofc camel/pascal case.
Bash, Python, etc., snake case, with constants as uppercase.
Filenames: I prefer snake case.