What's are you struggling with in particular? I feel like the Tokio devs would very much like to hear feedback if you're struggling with anything!
-
-
-
I would give anything to have garbage collection (yes) instead of having to use Rc, Arc, RefCell and clone() and boxes everywhere when using futures. That’s annoying, counterproductive and ugly as fuck.
- 6 more replies
New conversation -
-
-
I have mixed feelings about it. It's been useful for some code, but very hard to write and debug. For sozu ( http://github.com/sozu-proxy/sozu ) I probably won't move from mio any time soon
-
Carl is fitting mio to tokio now. The removal of timers and channels from mio was what forced me to rewrite edgedns using tokio. The end result was an unmaintainable mess over just using mio.
- 3 more replies
New conversation -
-
-
I looked at it frankly and decided to write my server without it. Since I don’t need super high performance I never bothered to head into future land. Plus I’m on OpenBSD so nightly is not an option. Did you consider ditching Tokio? (I assume yes)
-
May is more attractive, but the core team is pushing Tokio really hard. Other frameworks may stop being supported at any point in time. Tokio is more likely to remain actively developed, even though it may never get a stable API.
- 1 more reply
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Come back to C we have libdill :P
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This makes me feel like my impulse to learn mio first was the right one.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.