I also agree that tooling is a very important part. (although I don’t like my editor doing anything other than editing and syntax highlighting personally.)
Both Akka Streams and Flow promote backpressured async stream processing.
But Flow’s purpose is to behave and provide a DSL to support Map/Reduce and Spark like jobs.
Akka Streams supports more foundational lower level concepts. There are standard components, Source, Sink, Flow, Fan-in, Fan-out, along with a graph based DSL that lets you compose these components together in arbitrary ways, while supporting standard functional transforms like, map, filter, etc over streams.
With a standard component model you can start to build an ecosystem of data processors and connectors. Alpakka Documentation
If you like GenStage as a component model. Then these would be two DSLs that could sit on top of GenStage, providing a better developer abstraction.
You wouldn’t build the next generation of Phoenix on top of Flow. But you could/should with this new thing.
I’ve never used this, but i do wish hot code reloading or some framework to implement it was part of Elixir stdlib.
Does anyone know if Phoenix reloader is modular enough to work outside of Phoenix?
Try ExSync. it’s pretty good. It needs as much help with promoting it as with contributing.
@dimitarvp I’m not sure exactly if this is what you are looking for, but a similar feature is finding its way into ExUnit: https://github.com/elixir-lang/elixir/pull/8002