After 4 years with Rust, I love the language – but I’m starting to think the ecosystem has an abstraction addiction. Or: why every Rust crate feels like a research paper on abstraction.
@TehPers@cm0002 I guess I can somewhat empathize with the author. But you’re right, the author seems to be frustrated that some things are inherently complex. Though, Rust has terrific documentation and a lot of literature to get enough understanding to where things aren’t necessarily runes anymore, but rich in meaning.
I will say though, does nalgebra require custom derive macros? If you need to parse ast on the regular to use a library, I can definitely agree with his point on complexity.
I’m not aware of any custom derives needed to use nalgebra. I’ve never needed to write any. At most, I’ve written macro_rules! macros to help with trait impls, but not specifically for nalgebra.
I’m not too sure what the author is referring to there.
@TehPers @cm0002 I guess I can somewhat empathize with the author. But you’re right, the author seems to be frustrated that some things are inherently complex. Though, Rust has terrific documentation and a lot of literature to get enough understanding to where things aren’t necessarily runes anymore, but rich in meaning.
I will say though, does nalgebra require custom derive macros? If you need to parse ast on the regular to use a library, I can definitely agree with his point on complexity.
I’m not aware of any custom derives needed to use nalgebra. I’ve never needed to write any. At most, I’ve written macro_rules! macros to help with trait impls, but not specifically for nalgebra.
I’m not too sure what the author is referring to there.