Oh, well, I hope, it was clear that the third and fourth code sample aren't actually valid Rust, but yeah, I did write them to look like typical Rust production code.
And yeah, that article is great. I feel the same way, the semantics are just different. And whether you like those semantics, depends on what you're doing.
If you're just writing a quick script where you don't really need error handling and you probably won't have more than a few files etc., then Rust's semantics can be painful.
But if you're writing a larger application, then Rust's strictness and explicitness often just portrays the reality you have to deal with anyways. And it makes you deal with it right away, which can be frustrating at times, but overall feels like it boosts my productivity.
Oh, well, I hope, it was clear that the third and fourth code sample aren't actually valid Rust, but yeah, I did write them to look like typical Rust production code.
And yeah, that article is great. I feel the same way, the semantics are just different. And whether you like those semantics, depends on what you're doing.
If you're just writing a quick script where you don't really need error handling and you probably won't have more than a few files etc., then Rust's semantics can be painful.
But if you're writing a larger application, then Rust's strictness and explicitness often just portrays the reality you have to deal with anyways. And it makes you deal with it right away, which can be frustrating at times, but overall feels like it boosts my productivity.