Right now between this feedback and leorize I have 2 directions I can take this project. Given that either are a fundamental change to what it currently is, I archived the repository for now.
The question becomes whether I stick with either 1. having individual long-running microservice threads that can do async by having `poll(0)` in their eventLoop and just strip out the taskpool for simplicity so that the user can roll their own. Given I allow startup/shutdown events that users can use to initialize such pools that should be possible. Or B) I strip out the long-running threads and just make this an abstraction over status/nim-taskpools that can be used for all kinds of tasks including IO, given that they can send a message back when they're done, which is read from by the main-thread controlling the taskpool. For IO it would be mostly sync-IO that blocks that particular worker-thread until it is done. I'm struggling to make the decision here and I feel like that takes more than just a simple reading of a single blogpost to make. Though it did help put things a bit into context. The amount of additional understanding work required just makes it seem like basically I'm first supposed to do a couple months worth of studying besides work before capable of producing anything worthwhile anyone's time in that regard.
