I can't keep up with idiomatic Rust

Re:I can't keep up with idiomatic Rust by karatestomp on Thursday April 09, 2020 @09:01AM (#22822091)

You still have to understand all the new stuff to read other people’s code. And the old way, so you can read older code. And if there are other ways to do something that are or have recently been in common use, those too. You end up memorizing a bunch of crap for one actual operation.

[ Parent | on HN ]

Re:I can't keep up with idiomatic Rust by jrochkind1 on Thursday April 09, 2020 @09:05AM (#22822128)

Yep.

I think ruby (which in general I still love) has become a major offender of this. "If you don't like it don't use it" is not a good answer for exactly the reasons you explain.

[ Parent | on HN ]

Re:I can't keep up with idiomatic Rust by sgift on Thursday April 09, 2020 @09:20AM (#22822244)

I sense a goalpost moving here. The point of the blog post to which I answered to was: I have to redo all my programs to follow the "idiomatic" way.

Now we are at "other programmers could use new features, so I still have to learn them". And yes, that is true. And that will always be true as long as a language has new releases. Even if all those releases were library changes and not syntax changes/additions. The only way to stop this would be to stop all language development.

[ Parent | on HN ]

Re:I can't keep up with idiomatic Rust by setr on Thursday April 09, 2020 @01:12PM (#22824780)

Even worse would be if someone pulled in a library... That requires much more cognitive load and doc-reading than something like try! -> ?

Or the worst of all possible worlds -- pulling in a macro-based framework

[ Parent | on HN ]

Re:I can't keep up with idiomatic Rust by silon42 on Thursday April 09, 2020 @10:46AM (#22823023)

But you don't have to change your code unless it's an improvement to you. Somebody else may do it if they care, and you may accept OR reject the PR with no bad feelings.

[ Parent | on HN ]