> but i'm fucking confused every time I start reading its docs and syntax. You are not the only one. :) I definitely walked up to Rust & then turned around &

> but i'm fucking confused every time I start reading its docs and syntax. You are not the only one. :) I definitely walked up to Rust & then turned around & left again during my learning process. :D (And that was with the advantage of having dealt with manual memory management previously.) But I think the Rust community generally acknowledges the learning challenge that Rust may present at the beginning & work to reduce it over time. And also provide the reassurance that it's definitely not just you. At the beginning I think the resource I found most helpful was this: * <https://fasterthanli.me/articles/a-half-hour-to-learn-rust https://fasterthanli.me/articles/a-half-hour-to-learn-rust> Primarily because it's an extremely compact overview of Rust syntax which has the benefit of (a) improve your familiarity with the syntax & meaning to enable you to read Rust code; and, (b) it's all in one page so when one inevitably forgets something they can return to the page & search and/or review it. :) As the introduction puts it: > In order to increase fluency in a programming language, one has to read a lot of it. But how can you read a lot of it if you don't know what it means? > In this article, instead of focusing on one or two concepts, I'll try to go through as many Rust snippets as I can, and explain what the keywords and symbols they contain mean. It is also perhaps the shortest article by fasterthanlime on record. :D > Is it worth using rust for anything that isn't currently written in C? That's an interesting question. (FWIW C and C++ are also used for writing servers, command line & GUI applications.) One question I'd ask would be: have you run into the limits of any language you currently use in terms of capability, performance, packaging/distribution or community? If not, then perhaps Rust wouldn't currently be the best place to invest your learning time. But if there's some element of Rust that intrigues you, and you're kind toward yourself during the learning journey it's likely that at a minimum you may learn something about lower level aspects of computing that might help you when you use other languages. (One thing I've noticed with Rust is that--due to the power of the `cargo` build tooling & surrounding standardised library/crate ecosystem--once you get a relatively small way along your learning journey it can be relatively straight-forward to add a "cool"/"interesting" crate to your project & create something a bit more interesting than...a hard-coded currency exchange rate calculator or something. :) So maybe browse <https://lib.rs/ https://lib.rs/> (an alternative interface to crates.io which I find more "explorable") and see if there is a crate whose functionality makes you think "Ooo, that'd be cool to be able to use".) Good luck!