Discussion summary
FoundationDB's Flow introduces actor-based concurrency in C++11, but lacks widespread professionalization and documentation. Discussions highlight debates on concurrency models like coroutines versus actors, with some considering the approach outdated.
What the discussion says
- Some believe coroutines are better suited than actor models for modern C++ concurrency.
- There is criticism that FoundationDB's documentation and website are lacking.
- Others argue that actor-based models like Flow are still relevant despite newer concurrency features.
“It's weird that Apple, Snowflake, and others haven't invested much in docs or website.”
“Coroutines aren't great, even C++26 avoids them for concurrency.”
Comments
Hacker News
Why has FoundationDB not been professionalised? Better website, better docs, official GUI?
Is Apple responsible for preventing its wider uptake? Or alternative databases stronger?
by khurs
A previous discussion: https://news.ycombinator.com/item?id=46191763
by jen20
This looks kind of outdated, especially since we are on C++23 as latest approved standard, and co-routines would be a better approach since C++20.
Also how is the supposed Swift rewrite going on?
by pjmlp
Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- Why has FoundationDB not been professionalised? Better website, better docs, official GUI?
Is Apple responsible for preventing its wider uptake? Or alternative databases stronger?
by khurs - A previous discussion: https://news.ycombinator.com/item?id=46191763by jen20
- This looks kind of outdated, especially since we are on C++23 as latest approved standard, and co-routines would be a better approach since C++20.
Also how is the supposed Swift rewrite going on?
by pjmlp