I'm developing a unified enterprise-grade Rust development framework as an alternative to Spring. The core idea is to hide all complexity within macros, borrowing from Spring CI/DI approach.
To allow Java programmers to migrate to Rust without any mental burden.
I need your suggestions and your requirements for various business scenarios.

2 posts - 2 participants

Read full topic