141–150 of 203 posts
Best stack cloud providers don't want you to know about, /dev/null for db and https://github.com/kelseyhightower/nocode for the backend.
Idea: NaaS. Null as a service.
Reminds me of how in the math lectures, our professor would always point out he was ignoring the trivial solution[1]. That /dev/null is ACID compliant is the trivial solution of databases. Still, a jolly good read, and a nice reminder that concepts like ACID don't exist in a vaccuum. [1]: https://en.wikipedia.org/wiki/Triviality_(mathematics)#Trivi...
Except if it's in /dev/null?
Earlier quoted context omitted.
W just need R&D money to solve reading back from it, but that's just a matter of time we can definitely solve it in a year or two. This tech is just around the corner I promise, then we will be first to the market and all the big tech companies will want to buy us out, imagine how much we can earn. /s
If you have infinite time, you can find your data in /dev/random
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.
Depending on how you define "bash" and "bug", funny things happen when you run on a computer with 0 remaining hard drive space.
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.
Ah you've never encountered /dev/null not existing yet, so when you try to trash data it will actually create a normal file there so every other program that uses it will actually append that file. Luckily it's usually a tmpfs
I feel like that'd happen because of some other bug, I wouldn't consider that a bug in /dev/null :)
Reminds me of how in the math lectures, our professor would always point out he was ignoring the trivial solution[1]. That /dev/null is ACID compliant is the trivial solution of databases. Still, a jolly good read, and a nice reminder that concepts like ACID don't exist in a vaccuum. [1]: https://en.wikipedia.org/wiki/Triviality_(mathematics)#Trivi...
(hint: look up subnormal floats.)
It's also horizontally scalable: https://gist.github.com/raggi/560087#file-shardnull
It is also local first, low latency, data residency compliant, SOC2 compliant, zero dependency and webscale.
Does it have sharding? I heard sharding is the secret sauce for webscale.