Flux in .NET (Part II)

Thanks for commenting. I'll write something up. At the time, I had a working implementation with DataFlow, but then .NET Channels came out and it didn't seem to make sense to use Flux with DataFlow.

Your comment is very timely because I just finished doing some research and have 7 implementations of Flux working in .NET, so I think I'm getting a better understanding of the philosophy of it... In the end, it's nothing magical... and it doesn't seem to be anything ground breaking in terms of implementation, but I've realized that it's an architecture than can provide guarantees in your code about the state of the system - so the benefits is an increase in human productivity and reduction in bugs.

It's kind of funny because I realized that we don't need Flux, but we need it to enforce developer discipline - which is hard.

I'll get something written up in a few days.

Thanks for commenting again. It helps a lot to keep me motivated in writing.