Do you post the same on twitter?
Seems like you’re playing both sides…

This trade-off can lead to less stable builds if the updates aren’t carefully managed.

On the other hand, it introduces a maintenance burden: you or other developers might update that dependency in the future, potentially causing breakages or introducing vulnerabilities that the original maintainers never intended.

By explicitly declaring a previously transitive dependency, you’re taking direct responsibility for its version and compatibility. On one hand, this can ensure you know exactly which version you’re depending on.

Is it strictly Rust only ?

That’s a good strategy I hadn’t thought of that 👍🏽

1, 2, 3—except GraalVM. I tried it on a serious project; getting it to work was a nightmare. I eventually succeeded, but based on that experience, I don’t feel that Spring Boot + GraalVM native images are viable for production-ready apps yet. Your thoughts?