[dizon]

The problem occurs when I arrive on a landing page for a project re-invented in Rust that advertises not encountering double frees as a feature of the project. I notice the project is nothing more than a build tool for web development, and I just shake my head.

[nyanpasu64]

Personally I tend to use C and C++ tools more often, and in that universe, being statically free of memory errors is an innovation. In the webdev world, I suppose native speed and not having a large runtime or GC is Rust's primary innovation (though for batch jobs like build tools, a small Go-like runtime/GC isn't actually a negative compared to Rust, and I've never noticed GC pauses when I previously use the Micro editor in Golang).

[phendrenad2]

I'm sure any build tool for web dev can leak memory like crazy and it's fine, the OS will clean it up when the build tool exits. So Rust's features are wasted on that use case.

[dizon]

Exactly.