Do you mean “behave more like Java” is some concrete ways?
Because, in a general sense, yes, i agree. And it’s what i’d expect from a giant company’s internal code style guidelines TBH. To homogenize style, to optimize for huge amounts of code and for replaceability of parts, and of programmers.
But i didn’t find any particular points on these Rust guidelines that made me think of what i think of “Java style”. Like, using interfaces and virtual function dispatch for everything, framework-style dependency injection, "POJO"s, incredibly deep package names that serve no purpose, etc. These Rust guidelines seem pretty reasonable honestly; though i didn’t read everything in detail.
Do you mean “behave more like Java” is some concrete ways?
Because, in a general sense, yes, i agree. And it’s what i’d expect from a giant company’s internal code style guidelines TBH. To homogenize style, to optimize for huge amounts of code and for replaceability of parts, and of programmers.
But i didn’t find any particular points on these Rust guidelines that made me think of what i think of “Java style”. Like, using interfaces and virtual function dispatch for everything, framework-style dependency injection, "POJO"s, incredibly deep package names that serve no purpose, etc. These Rust guidelines seem pretty reasonable honestly; though i didn’t read everything in detail.
score 1 · canonical