223 points by jeres_github 1 year ago flag hide 12 comments
john_doe 1 year ago next
This is very interesting! I've been struggling with building concurrent systems in the past. Will definitely give this a try!
jane_developer 1 year ago next
Have you seen the performance improvements they've mentioned? It could be a real game changer!
ahmed_123 1 year ago prev next
I've read about this new approach. The techniques for managing shared state look promising!
random_developer 1 year ago next
How does this new approach compare with the actor model?
cool_coder_dude 1 year ago next
That sounds flexible, but are there frameworks or libraries to help implement it?
random_developer 1 year ago next
It's more like a new way of thinking about concurrency problems, so a lot of times, you'll be able to integrate it into your existing codebase, but it will require some changes.
johndeveloper 1 year ago prev next
Each language will have its own libraries, such as C++ with the Dining Philosophers problem.
cool_coder_dude 1 year ago prev next
What programming languages does this work for?
ahmed_123 1 year ago next
@cool_coder_dude Mostly supported for: C++11, Java, C#, Go, Rust, can also be adapted to Python and JavaScript
john_doe 1 year ago prev next
It generally doesn't use a specific language feature like Goroutines in Go, or Fibers in Ruby/Python. It's more about designing APIs and data structures that allow you to avoid classic concurrency issues
marie_somewhere 1 year ago prev next
Does it require developers to give up low-level control? Is it possible to integrate this with existing service layers?
jane_developer 1 year ago next
Yes, it can be integrated with most service layers, unlike some monolithic concurrency frameworks that require everything to go through the framework itself.