`cargo update mypackage@5` doesn't upgrade **to** v5 but selects v5 from your dependency tree if there is an ambiguity. A common case I run into: cargo add clap cargo add criterion # before it upgraded to clap v4 If you did `cargo update clap` it would error saying "which one?". Now its easier to type out which you wanted.
We tried Rust at work for a few weeks and stop using it due to low productivity. Our budgets don't allow to spend the time required with Rust versus extremely productive language like python
If your team is already productive in another language, it would not be unexpected for it to take months to reach an equivalent productivity in Rust, and that's okay. If you are already productive, it may not make sense to switch to Rust. However, when it does make sense, my courses will help you ramp up your Rust productivity much quicker! 😉
@@Jaime-eg4eb Sure, mixing Rust and Python in a short script would probably be a bit odd. It sort of depends on how deep you dig. A lot of the Python science modules are implemented in C. Rewriting portions of C in Rust can be worthwhile, as can choosing Rust for a new performance-critical module instead of writing another one in C. Replacing a large Python codebase with Rust to gain performance and reliability is a perfectly reasonable choice as well.
The announcement was Nov 8 on the Rust Foundation blog: foundation.rust-lang.org/news/the-rust-foundation-to-develop-training-and-certification-program/ Sounds like it's super early days. I reached out to the foundation and to Tim McNamara as mentioned in the post. We'll see if anything comes of it!
Hi, Nathan! Great video and thoroughly explained the update :) QQ: Since the Rust Foundation is developing its own training and certification program and is currently looking for Rust instructors, is it on your plans to join the program as an instructor? I enjoy your teaching methodology from your courses, and many would benefit greatly, especially when it comes to having a strong foundational understanding of the language :)
My guess: all the years. I, for one, welcome letting tooling handle more of the legwork. The job will morph a bit, just like it always does as new things are invented over time. We'll all need to continue to learn and use new and better tools, just like we always have.
These videos are so so good! Incredibly thorough, very well explained, and out on the same day as the release? WOW! Thank you Nathan
You are most welcome!
Amazing. Thanks for this content about Rust.
Loved your intro on Oreilly
You're welcome! Thank you for your kind words!
cargo update should really be named to cargo update-deps
Ya, the behavior of "update" subcommand is a bit unintuitive. I'm with you, there.
getting better every time. thanks
Hey, thanks! That's the goal!
Dear Nathan, as usual… splendid walkthrough! Appreciated :-)
Thank you for your kind words! You are most welcome.
`cargo update mypackage@5` doesn't upgrade **to** v5 but selects v5 from your dependency tree if there is an ambiguity.
A common case I run into:
cargo add clap
cargo add criterion # before it upgraded to clap v4
If you did `cargo update clap` it would error saying "which one?". Now its easier to type out which you wanted.
Ah! Thank you for the clarification, Ed!
We tried Rust at work for a few weeks and stop using it due to low productivity. Our budgets don't allow to spend the time required with Rust versus extremely productive language like python
If your team is already productive in another language, it would not be unexpected for it to take months to reach an equivalent productivity in Rust, and that's okay. If you are already productive, it may not make sense to switch to Rust. However, when it does make sense, my courses will help you ramp up your Rust productivity much quicker! 😉
A system language and a language used primarily for scripts and data science are usually not simultaneously good options to solve a problem.
@@Jaime-eg4eb Sure, mixing Rust and Python in a short script would probably be a bit odd. It sort of depends on how deep you dig. A lot of the Python science modules are implemented in C. Rewriting portions of C in Rust can be worthwhile, as can choosing Rust for a new performance-critical module instead of writing another one in C. Replacing a large Python codebase with Rust to gain performance and reliability is a perfectly reasonable choice as well.
Hello from number 36 onwards 16:24 when you talked about the clippy, how do you access those panels?
Thank you
It is the top result when you google "clippy lints". Here is the page: rust-lang.github.io/rust-clippy/master/index.html
It seems like you forgot to update video title to 1.74
Oops! Fixed. Thanks for noticing. 😄
Wonderful! Thanks
You're welcome!
The announcement was Nov 8 on the Rust Foundation blog: foundation.rust-lang.org/news/the-rust-foundation-to-develop-training-and-certification-program/
Sounds like it's super early days. I reached out to the foundation and to Tim McNamara as mentioned in the post. We'll see if anything comes of it!
Hi, Nathan! Great video and thoroughly explained the update :)
QQ: Since the Rust Foundation is developing its own training and certification program and is currently looking for Rust instructors, is it on your plans to join the program as an instructor?
I enjoy your teaching methodology from your courses, and many would benefit greatly, especially when it comes to having a strong foundational understanding of the language :)
Thank you for your kind words!
Answer to your question: They are!? I'll have to look into that! Thanks for calling that out!
With AutoGen, TaskWeaver, and the like, how many years left do we have a job?
Anyone care to guess?
My guess: all the years. I, for one, welcome letting tooling handle more of the legwork. The job will morph a bit, just like it always does as new things are invented over time. We'll all need to continue to learn and use new and better tools, just like we always have.