Live data from Hacker News

/dev/null is an ACID compliant database

jyu.dev

41–50 of 203 posts

Re: /dev/null is an ACID compliant database

#41

Best stack cloud providers don't want you to know about, /dev/null for db and https://github.com/kelseyhightower/nocode for the backend.

WTF is going on with the issues and pull requests for that repo?

They're using it to communicate in code to each other.

Re: /dev/null is an ACID compliant database

#42

I've used /dev/null for exactly this purpose. I have output that needs to go somewhere, and I don't want to worry about whether that somewhere can handle it. Later on in deployment, it will go somewhere else. Somewhere that has been evaluated for being able to handle it. In that way, /dev/null is to storage what `true` is to execution - it just works.

Bug free software is a pipe dream, but if there is anything I've never encountered any bugs with, /dev/null and true is certainly in the top 3.

False.

Wait: that's just not true.

Carry on.

Re: /dev/null is an ACID compliant database

#43
post #20

Earlier quoted context omitted.

I'm easily reaching 30GB/s with a single client: dd if=/dev/zero of=/dev/null bs=1M status=progress A second dd process hits the same speed.

What's the best hardware for running a /dev/null instance for production?

I usually do a kubernetes cluster on top of VMs. But sometimes when I really want to scale the standard cloud server less platforms all support /dev/null out of the box. (Except for Windows...)

Re: /dev/null is an ACID compliant database

#44

Earlier quoted context omitted.

WTF is going on with the issues and pull requests for that repo?

They're using it to communicate in code to each other.

Well they should stop that and start communicating in nocode instead.

Re: /dev/null is an ACID compliant database

#45

Best stack cloud providers don't want you to know about, /dev/null for db and https://github.com/kelseyhightower/nocode for the backend.

WTF is going on with the issues and pull requests for that repo?

The less substance there is to it, the easier it is to talk about.

The Chinese comments ("issues") also seem to be the same kind of jokes as the English ones, "no code means no bugs, perfect", etc., from the few I tried getting translations of. I imagine this went viral on Chinese social media, which makes sense since it's the sort of joke that's easy to translate and doesn't depend on particular cultural assumptions or anything.

Re: /dev/null is an ACID compliant database

#46

Earlier quoted context omitted.

Bug free software is a pipe dream, but if there is anything I've never encountered any bugs with, /dev/null and true is certainly in the top 3.

Joking aside I can’t ever remember seeing a bug in either bash or zsh, never seen either crash or segfault and anytime I’ve had weirdness it’s always turned out to be me missing something. Both (along with a lot of the standard utilities) are a testament to what talented C programmers plus years of people beating on them in unintended ways can achieve in terms of reliability/stability.

I've been able to trigger a segfault in zsh with certain plugins, a directory with a lot of files/folders, and globs with a bunch of * characters.

Re: /dev/null is an ACID compliant database

#49

/dev/null is not a database. By this logic is a hard disk a database, is a CD a database. No. They are storage mediums. You could store a database on them, but they themselves are not a database. Considering there is no way to read back data written to /dev/null it will not be useful for storing database data.

seems you've missed the joke
Post reply on HN