/dev/null is an ACID compliant database (jyu.dev)

Article summary

The article argues that /dev/null is an ACID compliant database, as it meets the criteria of atomicity, consistency, isolation, and durability. It always stays in a consistent state, which is empty, and any data written to it is discarded. The article is a humorous take on the concept of a database. The author notes that the only limitation is that it comes with 0 bytes of free storage.

Main themes

• ACID compliance
• Database systems
• Unix file system
• Humor in technology
• System reliability

What commenters say

• The concept of /dev/null as a database is a clever and humorous example of how a simple system can meet complex criteria.
• Some commenters argue that /dev/null is not just a database, but also a highly available and scalable system.
• Others point out that /dev/null is not without its limitations and potential issues, such as running out of file descriptors or memory.
• There is disagreement about whether the shell or terminal emulator should be responsible for ensuring a consistent display after a command completes.
• Some argue that a well-designed command-line interface would prioritize displaying the prompt consistently and reliably after each command.
• Others believe that the distinction between the interface and running program is useful, and that the shell should not be responsible for resetting the terminal state.
• A few commenters share personal anecdotes about encountering bugs or unexpected behavior in bash or zsh, contradicting the claim that these systems are bug-free.
• Some commenters note that /dev/null is not the only system that can be considered a database, and that other systems like Falso or devnull-as-a-service exist.