Thruster VS in-one-weekend

We've added support for the warp, salvo & thruster frameworks

Maybe, or maybe not, interestingly, I had to store async functions that call other arbitrary async functions for thruster. I tried many of the things posed in the article, and eventually ended up doing something similar to how bevy works -- that is, I made a bunch of tuples.

For a quick self promo, I've used thruster (https://github.com/thruster-rs/Thruster) for a few side projects with 10k reqs/day or so and I love it to death coming from nodejs land

Now for my shameless plug; I use a framework primarily that I maintain that aims to have the ergonomics of express or koa in rust. Try it out if you're interested: thruster.

If you'd rather wait for the next release (it'll be more like this afternoon rather than a year from now, promise!) I just fixed it in a PR here

I followed that tutorial as one of my very first Rust projects. Here is my GitHub repo: https://github.com/LoganDark/in-one-weekend

my implementation

I feel like this isn't just a case of people intentionally trying to ignore Rust's idioms, but just not knowing how to transfer over their existing knowledge. As someone who's learned over 15 programming languages throughout the years (rookie numbers, I know ;) it was relatively easy for me to learn Rust in about 2 weeks by diving straight into Ray Tracing in One Weekend (my implementation here), but I still feel like not many people could have done that, so I tend to hold off on assuming that they're intentionally trying to misuse Rust.