this post was submitted on 23 Jul 2024
32 points (86.4% liked)

Programming

17358 readers
254 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
 

YAML and TOML suck. Long live the FAMF!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 14 points 3 months ago (10 children)
[–] [email protected] 4 points 3 months ago (4 children)

That was my first reaction just by reading the title.

Mostly because I learned the hard way what inodes are.

[–] [email protected] 3 points 3 months ago (2 children)

Read the content. I address that issue.

[–] [email protected] 3 points 3 months ago* (last edited 3 months ago) (1 children)

For the record, you mention "the limitations of the number of inodes in Unix-like systems", but this is not a limit in Unix, but a limit in filesystem formats (which also extends to Windows and other systems).

So it depends more on what the filesystem is rather than the OS. A FAT32 partition can only hold 65,535 files (2^16), but both ext4 and NTFS can have up to 4,294,967,295 (2^32). If using Btrfs then it jumps to 18,446,744,073,709,551,615 (2^64).

[–] [email protected] 1 points 3 months ago

You are right. Fat32 is not recommended for implementing FAMF.

[–] [email protected] 1 points 3 months ago

I know, I read it because I wanted to know too know if it was addressed

load more comments (1 replies)
load more comments (6 replies)