Thank you!

Well, I cannot call myself a traditional OOP dev, I've been advocating for mixing OOP and FP for quite a long time :)

- Reinventing the wheel still sounds a little bit negative. I would prefer to call it an evolution :) At the same time, at least in my opinion, BLoC has nothing (ok, little) to do with MVC/MVP/MVVM, it's not a controller/presenter/view model, it's an entity that does business logic and handles app state, as opposed to rather "view" state in presenter/view model.

- If the architecture seems to be complex, probably I failed to explain it properly :) I believe that the idea is quite simple – it's essentially just a State Machine with a Sink for events and a Stream of app states. As for the data layer – as I mentioned, it's optional, if there's a straightforward mapping between your app models and backend DTOs, your BLoC can communicate directly with the API layer, in that case it's just View (Widget) – Business Logic (BLoC) – API.