jitans

Why don't use fu2? https://naios.github.io/function2/

I would have used CockroachDB, it has all the requirements listed and you don't need to know in advance the queries you will perform when deciding the database schema.

not even all the "traditional" databases, each Engine has his own peculiarities.

And why don't you make a FB account?

So basically what we needed was a different email client?

Do you realize WhatsApp privacy hasn't changed?

And leaking a mail (with real names) is much better?

Just because this is the new trend (for no reason) ?

This should have been: PostgGRPC

Why your application doesn't use a view? Or even better a table function?

This is one of those features to not use ever, unless you have another problem that is an application touching directly a table instead of a view.

If you use a compiler do not ignor ever ever the warning messages. Aim, from day 1 to have a compilation warning free. Write code to be read by humans, and do not ignore writing testing code, more or less you should have twice code in testing than real code under test.

There is who cares about his data and who uses MySQL

They haven't any custom driver, CRDB is binary compatible with postgresql drivers, are marked as beta because "maybe" there is feature they haven't implemented. So far using pqxx (C++ driver) I haven't seen any issue.

In postgres you can choose if the replication is synchronous or asynchronous. For cascade replication (a slave uses as a master for another slave) the replica is always async.

Instead to improve the "use" they had to remove it and enable only namespace renaming

well the demo then is broken indeed it shows still an "a" inside the multiset. Having say that I would never use a cuckoo in a multiset, indeed it becomes a bounded multiset. Also about the K-hashing for a bloom filter is not exact. You just need need a K-bit hashing function. If the goal is to support deletion then I would go for a Counting Bloom filter

Add five "a", now remove four "a" Cuckoo claims there are no "a" in the multiset...

That's not the point. Trying to squeeze the code in less lines as much possible is not the way to go if you loose clarity. Python coders keep repeting the mantra "less line of code" but in the mean time they keep typing: self. self. self.

As you can see we are the only one thinking this is absurd :D

how stupid is to measure code in terms of lines?

Make all that a library then you can claim:

A static site generator in only 3 lines of Python

Measuring lines of codes is completely wrong. See the Scala trend were people race to find the shortest way to express something generating hard to understand code. 1) Code has to be written to be maintenable. 2) Code has to be written to be read by your coworkers. 3) The bottleneck while coding is not the keyboard.