Too many possibilities for the same, is it good?

[MOCKBA]

It is wonderful explanation. Indeed, I use Rust mostly for a web development. So my tool to see my work is a web browser. When I use 'cargo run' , I actually launch a browser. Funny thing that a browser is already on screen and I even do not refresh the page, I just continue using the developing app, but now it behaves differently after I changed my Rust code. If I do a debug print out, I do not see it on screen or in some log file. It's probably different than other developers do. Anyway, my way of using Rust constructions is similar to yours. I started from brutal unwrap which later migrated to is_ok and then to 'if let' and finally to 'match'. On a similar note, I migrated from 'if else' to 'when' when I use Kotlin. I also like Rust transparency using exactly same constructions when work with different data structures. For example, I implemented something using arrays, however I was requested to use vectors after some time. I was scared that it will require lot code changes, but those was zero, I only changed data definition.