mxey
mxey on Hacker News
Seems to me that “we ran the Jepsen test” is just something an LLM thought would sound good on a DB’s website.
It’s wild how bad it is. Not surprising for a vibecoded database, but why did they hire Kyle for a test, instead of first doing ANY testing themselves?
“isolated environments on shared hardware”
So, not isolated environments? The surprising thing is that they used the CPU cache instead of the just exploiting the hypervisor.
You can cut out the middle man and use
https://github.com/marxarelli/masse, a CUE frontend for BuildKit.
However I don’t think anything using BuildKit is as fine grained as Bazel.
“Their tests showed that rqlite maintains linearizability of record insertion and modification, provided strong read consistency is enabled.”
The rqlite docs however tell you to never use Strong mode and that Linearizable is sufficient. https://rqlite.io/docs/api/read-consistency/#strong
How are agents helping you? What was the trouble with Postgres before?
Many CVEs have too high severity for what they describe.
“They can put SCTs in the cert, and still not publish to the logs, nobody is auditing the logs for every cert every browser sees”
I don’t think you can get the SCT from a log without the log publishing it? That would defeat the purpose.
“Certificates that support certificate transparency must include one or more signed certificate timestamps (SCTs), which is a promise from a log operator to include the certificate in their log within a maximum merge delay (MMD).[4][3] At some point within the maximum merge delay, the log operator adds the certificate to their log.”
The majority of existing software runs without a glitch? Are you being serious?
Who writes those tests and makes sure they test the right thing and everything?
That’s an interesting idea but not all locks are held for the duration of the statement. A lot of them take a less intrusive lock for the whole statement and take an exclusive lock for a very short time when they finish up.
Edit: Looking this up, I’m not sure this is correct.
> The WireGuard website claims ChaPoly is at least as fast as hardware-accelerated AES.
I haven’t used WireGuard but I have easily doubled OpenSSH performance by switching back to AES.
Since 10.7 it autosaves.
The Delete button is shown, and correct, for new files that have not been saved at all yet.
The drain is asynchronous, so it won’t block.
The limit is 256 KB and 50 ms.
At which point there’s little difference from any other database’s backup commands.
I think the SQLite website itself says it best:
> SQLite does not compete with client/server databases. SQLite competes with fopen().
The Compose file is written like that so you can quickly try the app without setting up extra dependencies. Usually not for production use.
Especially since in production you might want to scale the parts separately. I like to have a Postgres cluster to connect where backup is already handled, and the app then doesn’t have any persistent data, doesn’t need any network volume mounts.
Yes if you run a database server like an embedded application database, then it won’t be very different from an embedded application database.
SQLite in WAL mode which you want for server apps is multiple files.
Files which you cannot just copy while your application is running if you want a correct backup.
Yes, initially modules used to modify the file automatically which is why I have -mod=readonly in some old pipelines.
I think the “new” way is much better.
I still run tidy in pipelines to check but that’s only for cleanup.
> It only syncs go.mod with what is already being used by the build process
If dependencies are incomplete, Go will fail to compile and tell you to run go mod tidy to fix it.
Pinning to me means there is a file with all the versions as they will be used. I don’t see how “go mod tidy” modifying it is different from “bundle install” modifying it.
> You literally cannot dereference an Option without acknowledging the None case. Whole categories of pager-duty incidents disappear.
This is at the very least misleading, given that you can use unwrap.
Regarding error handling: will a parser error in the config return an error that includes the name of the file that’s failed to parse? That’s the kind of useful context that I add to errors in Go.
Actually with Go modules you are always pinning dependencies. What’s in your go.mod is what is used. If your go.mod needs to be updated because a dependency wants to bring in a newer version of a transient dependency, the go.mod has to be modified (by the go command, not by you)
That’s the opposite of clean-room. The whole point of clean-room design is that you have your software written by people who have not looked into the competing, existing implementation, to prevent any claim of plagiarism.
“Typically, a clean-room design is done by having someone examine the system to be reimplemented and having this person write a specification. This specification is then reviewed by a lawyer to ensure that no copyrighted material is included. The specification is then implemented by a team with no connection to the original examiners.”