3 ms·
I get to see a lot of folly code, since I'm at Facebook. It's mostly improved implementations and semi-obvious extensions of things that already exist in the C+
by notacoward 7y ago
I get to see a lot of folly code, since I'm at Facebook. It's mostly improved implementations and semi-obvious extensions of things that already exist in the C++ standard library, plus prototypes of things that will be in the next standard. Much like boost. While this is mostly good, it has to be said that improved implementations of bad patterns from the C++ standard (especially around concurrent programming) aren't something I'd spend my own time on. Life's too short to invent a better square wheel.
- sriram_sun 7y agoI don't want to end up splitting hairs over terminology so please correct me if I'm wrong. I would like expect a c++ library (folly or the standard library) to provide concurrency primitives and not patterns. Once you start providing patterns you are wading into framework territory. Is that the case with folly?
- hellofunk 7y agoThe C++ standard has included threading primitives since 2011. Many libraries exist that create higher level of abstractions, i.e. patterns, on top of these primitives. But you can also just use the primitive directly.
- notacoward 7y agoUnfortunately yes. The whole way that futures and "EventBase" are tangled up makes them more of a framework (and not one I would use if I had a choice) than a set of primitives. https://github.com/facebook/folly/tree/master/folly/io/async https://github.com/facebook/folly/tree/master/folly/io/async
- sriram_sun 7y agoThanks! I was going to ask "Does folly have its own asyncio for e.g." :)!