3 ms·
I 100% agree with the other comment: Abseil and Folly are both broken monstrosities by design... the build system garbage is just one reason almost nobody uses
by jcalvinowens 2y ago
I 100% agree with the other comment: Abseil and Folly are both broken monstrosities by design... the build system garbage is just one reason almost nobody uses them outside facebook and google.
The chaining hashtable in liburcu is truly lock free, based on a real build system, and in my experience outperforms everything facebook and google have ever published: https://github.com/urcu/userspace-rcu https://github.com/urcu/userspace-rcu
- jeffbee 2y agoCalling cmake, bazel, and buck "garbage" while recommending an autotools project is one way to have a take, I guess.
- nemetroid 2y agoA pretty reasonable one, too. Getting liburcu to build is trivial.
- jeffbee 2y agoIt is also pointless, because the question is not how to build the library, the question is how to integrate and reference it in the project where you want to use it.
- jcalvinowens 2y ago...yes, and that problem was completely solved a decade before Bazel and Buck reinvented a shittier wheel. You don't have a leg to stand on here. I can build and run liburcu on everything. You can barely build Folly on FreeBSD...
- nemetroid 2y agoSure, and packaging the artifacts of the liburcu build is going to be trivial in any package management system. It makes very few assumptions about how it's going to be used. Using Folly requires you to ascribe to the Folly worldview of dependency management. Abseil isn't too bad.