I don't see the "use sparingly" conclusion. It's a complex trade-off of runtime performance, code clarity, productivity, safety, binary size, and compile times

I don't see the "use sparingly" conclusion. It's a complex trade-off of runtime performance, code clarity, productivity, safety, binary size, and compile times. Rust tries hard to eat all the cakes and have them too, but it can't do miracles. And looks like the author is on the right track to tackling the problem — moving less common functionality behind feature flags, pregenerating data "offline", profiling and trimming code with the help of cargo-bloat.