Live data from Hacker News

/dev/null is an ACID compliant database

jyu.dev

101–110 of 203 posts

Re: /dev/null is an ACID compliant database

#102
post #6

Earlier quoted context omitted.

I guess we have a perfect idea for vaporware here. (pun intended) I am putting my marketing hat on right now.

You've been beaten to the punch: https://devnull-as-a-service.com/

It's down!

    $ telnet devnull-as-a-service.com 9
    Trying 2001:19f0:6c01:497:5400:ff:fe69:8cbf...
    Connection failed: Connection refused
    Trying 45.76.95.197...
    telnet: Unable to connect to remote host: Connection refused

Re: /dev/null is an ACID compliant database

#104

Earlier quoted context omitted.

Did you route the support requests to /dev/null as well?

Haha, I guess support.google.com is an ACID compliant database as well.

My /dev/null of choice is https://github.com/orgs/community/discussions/

Re: /dev/null is an ACID compliant database

#107

/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.

[dead]

Re: /dev/null is an ACID compliant database

#108

In a similar vein, this is one of the most interesting things I’ve come across on HN over the years: https://www.linusakesson.net/programming/pipelogic/index.php Past HN post: https://news.ycombinator.com/item?id=15363029

I hadn’t seen this before, this is sick! thanks for posting it here :)

Re: /dev/null is an ACID compliant database

#110
post #77

Earlier quoted context omitted.

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 had a fun bug where bash would run scripts out of order! This would lead to impossible states, like if cat foo | false; then echo hmm; fi Producing output sometimes, depending on whether or not `cat foo` or `false` return value was used [0] https://lists.gnu.org/archive/html/bug-bash/2015-06/msg00010...

This was an interesting read.
Post reply on HN