So out of the 3 points, 1 is not an actual problem, but just learning curve, 2 is a mostly complete, but slightly limited mocking library, and 3 is an unoptimized local dev/build process.<p>I actually think those are fair reasons to switch to something more straightforward for a solo dev, but none of these are true showstoppers and the story for each will get better in time. Good feedback on the Rust in general.
> <i>I have two options: either throttle my whole computer by spinning up a massive image for Rust to compile in, or deal with 3+ minute compile times. My dev cycle grinded to a halt, and I felt incredibly unproductive. I tried changing my workflow to write the code and the test before manually testing, or to not use auto-hot reload, but I felt cripped. I just couldn’t do it.</i><p>Can someone explain that part to me like I'm an idiot?<p>I don't get it. Compiling the project is slower on a container because...?
Yes, compiled managed languages are much better suitable for distributed computing workloads.<p>Leave Rust for use cases where no form of automatic memory management is desired.
I'm far from a Rust expert but isn't 1. Just solved with traits? And 3 seems more of a bad project structure they have chosen, containers have their place. But it's not local dev.