I've written a few Rust programs. It's a good language with some really nice touches - its match and enum constructs are excellent. It is quite verbose though and while you fight the compiler less...
I've written a few Rust programs. It's a good language with some really nice touches - its match and enum constructs are excellent. It is quite verbose though and while you fight the compiler less the more code you write, it's certainly more restrictive than pretty much any other language out there. That said, it's extremely satisfying to know that when your compilation is finished you're left with a binary that's both extremely performant and highly resilient.
I used it a bit. Its a very well designed language and solves a lot of hard problems while remaining lightning fast. The issue I had with it is that its really hard, there are a lot of complex...
I used it a bit. Its a very well designed language and solves a lot of hard problems while remaining lightning fast. The issue I had with it is that its really hard, there are a lot of complex rules you need to understand to use rust. Once you spend the time to learn it you should be good but others have also pointed out that it takes longer to learn than most languages. Thats why Go is so popular, its still very fast while not being so hard to learn. Rust likely runs faster and has more safety features than go but many people are willing to make that trade off for faster learning.
Biggest hurdle with learning Rust is internalizing the borrow checker, which is not really a part of any other common programming language. But after some time (I have heard week or two of active...
Biggest hurdle with learning Rust is internalizing the borrow checker, which is not really a part of any other common programming language. But after some time (I have heard week or two of active use quoted on job context) of learning what the borrow checker wants, you mostly stop fighting the compiler and let it help you instead.
How much you actually have to care about the borrow checker really depends on what you are doing though. If you don't need to write complex memory structures or can get away with cloning memory everywhere, it gets much easier much faster.
Rust is still fairly verbose language, and using it for quick hacks is probably not actually worth it (I do it anyway though, because I like the language).
I quite like this post by Bryan Cantrill of DTrace fame, because it talks about a lot of aspects of rust that aren't just the borrow checker, which you'll definitely have heard about if you've...
I quite like this post by Bryan Cantrill of DTrace fame, because it talks about a lot of aspects of rust that aren't just the borrow checker, which you'll definitely have heard about if you've done some reading about learning Rust. Obviously at the end he concludes that Rust is great, and you should learn it, but he also talks about some problems you may run into and things to avoid.
I've written a few Rust programs. It's a good language with some really nice touches - its
matchandenumconstructs are excellent. It is quite verbose though and while you fight the compiler less the more code you write, it's certainly more restrictive than pretty much any other language out there. That said, it's extremely satisfying to know that when your compilation is finished you're left with a binary that's both extremely performant and highly resilient.I used it a bit. Its a very well designed language and solves a lot of hard problems while remaining lightning fast. The issue I had with it is that its really hard, there are a lot of complex rules you need to understand to use rust. Once you spend the time to learn it you should be good but others have also pointed out that it takes longer to learn than most languages. Thats why Go is so popular, its still very fast while not being so hard to learn. Rust likely runs faster and has more safety features than go but many people are willing to make that trade off for faster learning.
Biggest hurdle with learning Rust is internalizing the borrow checker, which is not really a part of any other common programming language. But after some time (I have heard week or two of active use quoted on job context) of learning what the borrow checker wants, you mostly stop fighting the compiler and let it help you instead.
How much you actually have to care about the borrow checker really depends on what you are doing though. If you don't need to write complex memory structures or can get away with cloning memory everywhere, it gets much easier much faster.
Rust is still fairly verbose language, and using it for quick hacks is probably not actually worth it (I do it anyway though, because I like the language).
I quite like this post by Bryan Cantrill of DTrace fame, because it talks about a lot of aspects of rust that aren't just the borrow checker, which you'll definitely have heard about if you've done some reading about learning Rust. Obviously at the end he concludes that Rust is great, and you should learn it, but he also talks about some problems you may run into and things to avoid.