The Rust Release Cycle Explained

Ғылым және технология

Today we are going over the Rust release cycle, which is important for all Rust developers to understand!
#rust #programming #tutorial

Пікірлер: 21

  • @letsgetrusty
    @letsgetrusty Жыл бұрын

    📝Get your *FREE Rust cheat sheet* : www.letsgetrusty.com/cheatsheet

  • @glebbash

    @glebbash

    Жыл бұрын

    Trading personal information and automatically opting-in to emails is not free. I am getting annoyed every time I hear this. Otherwise good content.

  • @AmnesiaPhotography
    @AmnesiaPhotography Жыл бұрын

    Great vid as always. How about a vid on minimizing the file size of a rust program. Eg release plus strip the executable of symbols. I was surprised on the file size for a simple ls app I wrote. Tons of error messages in there but was still 260kb was thinking it would be smaller

  • @letsgetrusty

    @letsgetrusty

    Жыл бұрын

    Great idea!

  • @thingsiplay
    @thingsiplay Жыл бұрын

    To me the Rust Editions concept is one of the best features of Rust eco system. In addition to these concepts, the promise of Crates io to not delete or change existing versions of crates is the tip of the iceberg. All of these compatibility features will pay off far in the future, where you can use any existing crate and combine with anything in the future, without the need for updating old code. And that is only one of the best features Rust has to offer. I don't understand how people get mad at the Rust language...

  • @AediusFilmania

    @AediusFilmania

    Жыл бұрын

    they are mad, because they are jalous.

  • @christopheriman4921

    @christopheriman4921

    Жыл бұрын

    To be honest I only really dislike the syntax that rust uses, I like the syntax for C++ better for functions, switch/match statements and variable declaration since I like explicitly defining types before the variable name and function name. I definitely would use it more if it were more familiar in terms of those things since C++ does generics in a slightly easier to understand way for simple functions.

  • @thingsiplay

    @thingsiplay

    Жыл бұрын

    @@christopheriman4921 I can imagine in the future alternative languages that uses ideas from Rust. Or even like TypeScript that is essentially creating JavaScript, so something like Rust++ could from C++ like language Rust code. The more popular it gets, the more likely this to be happen. I think you are not the only C++ programmer who would like to have advances from Rust without changing your C++ flavor.

  • @christopheriman4921

    @christopheriman4921

    Жыл бұрын

    @@thingsiplay I am definitely willing to change up my syntax that I use but for me as of currently it is a bit more change than can handle all at once. I initially started programming with Java and moved to C++ soon after since Java was much more annoying to work with when everything is a class and it adds a bunch of stuff that is unnecessary. Although I will say Java was much easier to get a GUI app up and running with despite the issues I personally had with the language. It really would be nice if there were several versions of rust that try to get close syntax to that of other languages like C++ for those that like the ideas behind rust and just don't like the syntax.

  • @thingsiplay

    @thingsiplay

    Жыл бұрын

    @@christopheriman4921 If you ever dive into Rust, you will notice that the syntax is the least thing changing for you. The entire logic how to program and think has to change from C++ to Rust. There are not classes. The entire lifetime thing will cost your some hair, if you think syntax is the biggest change. And I am telling you that with the best intentions. I used Python mainly scripting stuff and a few bigger programs, even some fancy gui with Qt5. And as you know that syntax is way different and it was still no issue.

  • @uovo
    @uovo Жыл бұрын

    it makes me so happy to have such high quality content for free, thank you Bogdan

  • @netify6582
    @netify6582 Жыл бұрын

    Great explanation as always!

  • @0xhiro
    @0xhiro Жыл бұрын

    Awesome video ✌

  • @eloylp6012
    @eloylp6012 Жыл бұрын

    Thanks for your great content !! 👌

  • @jeffg4686
    @jeffg4686 Жыл бұрын

    I never really "got" editions. This solidifies that for me. Why don't they just use the "major" number in the release number - isn't that the 'semantic versioning' rule? (and do away with "editions"). I don't know - having only one thing to have to think about is better than 2 with some stuff. With versioning, I thought SV was supposed to solve this. I'm not desiring to 'rant' here, as I think the team is kicking ass in all regards - just left wondering why here, and slightly confused, but not mad - yet... Then again, maybe this is one of their many "halt points of confusion" for those they don't want to make it. "... give 'em a few more things to think about, most will drop ..." (unfortunately, they ALL drop ... eventually!)

  • Жыл бұрын

    Thank you

  • @EvanCarrollTheGreat
    @EvanCarrollTheGreat Жыл бұрын

    You present it here as if rustc will always support every edition of Rust. My only critique here is that this is not true. At some point of time rustc will drop support for antiquated editions of Rust. At this point of time, rustc will increment the major version number, as it is itself under semantic versioning. So your project is versioned to an edition which can be thought of as a language standard which is supported by rustc. Rust 2018 can be compiled by any version of rustc with support for Rust 2018. Rustc has no obligation to carry every edition moving forward, and there will be difficulties when it drops an edition. =) Moreover, not every compiler will support every edition of Rust (rustc isn't the only one).

  • @ahmedhassane2369
    @ahmedhassane2369 Жыл бұрын

    hi bro I just want to know if there is a way to compress a file with a password, or if there is an example that can help me I searched but did not find anything interesting with which I'm comfortable with

Келесі