Heh cool, think I've now helped author around 10.000 lines of modern Futures code! Did a quick Tokei search on the codebases I work on, and it's pretty close! Whew!
-
-
Gave up on Rust? Yeah. I thought that if my experience was representative for the language, then it was simply too hard for me to ever be able to express myself freely enough. Luckily I decided to become proficient in sync Rust first at some point, and yay that worked well!
Show this thread -
I'm very happy how far we've come. Modern futures feel very simple. Even Pin is easy enough if you just consider it a black box that says: "this makes it so Futures don't require to be heap-allocated." There's 1 arg, which is a callback. Its return type is essentially an Option.
Show this thread -
I'd be very sad if we were to move away from this model. I feel like the current model is beautiful in its simplicity. Writing it by hand isn't a chore at all; it's actually really nice (as in my first tweet: I've done this *a ton*).
Show this thread -
Because yeah, it's being considered to move away from this model. And one of the reasons is that "implementing Futures aren't an end-user interface". Which just bringing that up makes me feel sad Idk if it's quite gatekeeping but it feels like it neglects the need for simplicity
Show this thread -
Like: I strongly believe that every part of a system ought to be understandable. Just like every layer of a building needs to be solid, so do the layers in our systems. There will always be tradeoffs. That's our reality. But I wish making systems understandable was weighed more
Show this thread
End of conversation
New conversation -
-
-
Thanks for sharing. Really helps as I'm just getting starting with Rust and feeling a bit overwhelmed

-
Yay, glad it was helpful. Tbh I felt the same way when I was getting started, but found that after a few weeks of really going at it it got a lot better. And now a year or so later I'm almost as comfortable with it as with JS :D
End of conversation
New conversation -
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.