The Complete Rust Programming Course (Udemy.com)

This was generally a good beginner Rust learning experience for me. I had no problems grasping the new concepts, enjoyed Tyler's talkthrough as he coded, and came away feeling as though I got a good foundation. CONS: 1. I wasted a lot of time transcribing code during the second half of the course simply because the github repo didn't provide all of the code he wrote. This meant hours of rewinding and playing back the videos, zooming in to see difficult-to-distinguish syntax, and switching back and forth to my own coding window. If *all* of the code for the course had been included on github, I would have finished the course in half the time and would have been able to focus far more on learning Rust on the first pass than transcribing code (and listening to the instructor and really learning on the second pass). 2. Screen font was far too small. This wouldn't have been as important if (1) hadn't been the case. Part of this came from teaching via an IDE, which also kept popping up and obscuring the code I was frantically transcribing due to (1). 3. Clearly some of the material had gone out of date. This made the wasm exercise mostly pointless - I couldn't complete it. It was also difficult for me as a beginner to figure out that, say, a command such as "cargo generate" had changed since 2022. => Update the material now and then! PROS: 1. Tyler knew his subject cold, and I had complete confidence in his own Rust abilities. 2. He spoke clearly and was pretty easy to follow. I have taken other courses from instructors with thick accents or poor diction; being able to hear and understand the instructor as he typed and taught made all the difference. 3. Great value for the $.

In Deutsch: Also ich bin fast durch, und ich habe viel gelernt. Das ist gut, in Summe ist der Kurs empfehlenswert. Ich hätte nur folgende Verbesserungsvorschläge: - Kapitel WebAssembly: Die Funktionalität scheint in Rust kaputt zu sein, ich bekomme das WebAssembly nicht zum Laufen, und das scheint vielen so zu gehen. Es wäre gut, wenn dieses technisch realisierte Assignment entfernt würde. - Assignments generell: In den ersten Kapiteln waren Assignments mit Bewertungen von anderen Lösungsvorschlägen. Super! Wieso nicht bei den späteren Kapiteln? - Kapiel 22 Verkettete Listen: ich dachte zuerst, was soll das, wozu verkettete Listen? HashMaps, Vektoren, BTrees usw. können das Gleiche nur viel schneller, und bei Verketteten Listen muss man vermutlich bei Asynchronous Rust (Tokio und Konsorten) höllisch aufpassen, da ich mir nicht vorstellen kann, dass die Listen unpin implementieren (und daher die Zeiger auf next kaputt gehen). Das Kapitel war dennoch gut, und das kam ganz am Schluss raus, weil er uns die Funktionsweise des Stack näher gebracht hatte. Mein Vorschlag: Kapitel umbenennen und so aufziehen: Der Stack ist mega wichtig, weil ... und um das zu verdeutlichen, wie ein Stack funktioniert, bauen wir eine verkettete Liste... - Sortierungsalgorithmen Der Q-Sort wurde im Beispiel nicht auf eine Weise implementiert, dass die Collection, an welche die Methode aufgerufen wird, sortiert wird, sondern es wird ein sortierter Vektor zurückgegeben. Ich habe so eine Ahnung, wieso, denn es ist praktisch unmöglich, zwei oder mehr mutable Referenzen auf dieselbe Collection zu erzeugen ohne die Verwendung von rohen Zeigern. Vielleicht darauf hinweisen. Oder als Beispiel für unsafe Code verwenden. - Graphen: In Abschnitt 26 wird erklärt, dass der Graph im Rechner mit einer Adjazenz-Matrix dargestellt wird, und wir das so implementieren. Das stimmt nicht: Weder wird die Matrix in der Praxis verwendet (sondern man verwendet Adjazenzlisten) noch wird eine Matrix im darauffolgenden Kapitel implementiert, sondern die Adjazenzliste. Also die Introduction anpassen. - Graph: DFS-Algorithmus: Wir bauen in Abschnitt 26 einen Graphen und bauen für Abschnitt 27 noch einen Graphen und üben daran den DFS-Algorithmus. Wieso wird nicht der Graph in 26 verwendet? - Rekursionen: Ich stelle die O-Notation (Komplexität) der verschiedenen Algorithmen nicht in Frage. Es ist nur so: Rust mampft auch Türme von Hanoi mit 200 Scheiben weg, und das in derselben Zeit wie 3 oder 4 Scheiben, also wenigen Millisekunden (wenn man mit cargo --relase) kompiliert. Die Anzahl der errechneten Züge stimmt mit der Literatur überein. Bei 200 Scheiben ist eine Grenze erreicht, weil die Anzahl der Züge nicht mehr in u128 dargestellt werden kann. Mich würde interessieren, wie das geht. Einfach den Code aus dem Beispiel nehmen und mit cargo --release kompilieren. Und damit der Compiler kein Inlining vornehmen kann, die Anzahl der Scheiben vorher in der Konsole einlesen. Gleiches Ergebnis. In C benötigt derselbe Code (1:1-Portierung) x^n Züge (also verdammt lange). - Mikro! Geben Sie mir Ihre Adresse, ich schick Ihnen ein Mikrofon zu.

The course covers the basic concepts and the generic syntax of Rust in a very clear and concise way. The assignments really help to get in touch with the topics explained in the lectures. However at some point of the course, when talking about more "generic" programming topics such as sorting, lists and so on... the coding lectures are more of a "typing rush" as a lot is written but not really explained; I mean the theoretical concepts are clear, but it's really hard to understand what is being written, especially when learning a completely new programming language. Beside this, I have really enjoyed the course and I would recommend it to anyone who wants to begin learning about Rust.

Was disappointed with the WASM section. The npm libraries had some breaking changes that caused the experiment to fail. I tried with the current npm and was not successful :(. Still 5 stars for the course at this price.

great explanation! great and simple examples, useful use cases. Sometimes I lost focus on telling because of nothing was happened on the screen, just explaining in words. Maybe, it will be better to have some illustrations fro that moments.

A real good course on Rust, that goes from the first steps to already advanced knowledge, I really liked this course, I would only hope that the teacher had more courses to follow up this one in Rust. Best regards, João Carvalho

The Macros section definitely went all over my head, didn't understand a single thing. Instructor just spat out all the code without any explanation. I felt it was a totally new syntax so should have rather taught how to write in that syntax so we are able to write any macros on our own. Simply bombarding all the code and then just saying a line about what's happening doesn't help at all. If at all, it potentially drove me away from ever getting into macros now..

The course is overall very good and I enjoyed it quite a bit. I already had some Rust experience (reading the Rust Book up to the "simulating object-oriented stuff" part) and have been programming in other languages for a while. So, my experience is colored by that background. I typed everything along with the instructor, even though all the code from the course is available for download, because I learn better that way. I suspect that people with no programming experience might feel a bit lost in the course at times, even though the material starts from the basics of programming. A few things are rushed or not explained in more detail (for example, in the implementations). I got a lot of it from previous experience, but there is a lot that I still do not know why it was done the way it was. But I suppose that's unavoidable, given the breadth of the material covered --if everything was explained in detail, the course would be way too long... A few more problematic areas I found and can recall now follow. The async part uses an example that is way too complex and I got lost with so much stuff... I think I understood it after all, but I'm not completely sure. The dynamic programming part... well, I do not know how to define dyn. prog. until now, since that was "explained by example", which did not work in this case, at least for me. So, overall, a very good course that I recommend to anyone (especially if already experienced in programming) who wants to learn a lot about Rust.

If you are a beginner or intermediate, sections 1-16 are worth the price of admission. Solid course, concepts are well and thoroughly explained. Until you hit the Section 17 project... Rushing through, typos and mistakes, "monolithic" instead of "organic" demonstration method, minimal explanations and using language features not covered in the course prior. On the whole, worth it, just hope the instructor continues to add to the course and maybe considers redoing the chat app section.

Very fast paced course. Some of the lectures in the async rust module was little difficult to follow and had to do some googling because of the rust syntaxes. I would recommend the instructor to maybe increase the font size and also show only the editor during coding and not file tree. Other than that loved it. Recommend to anyone who wants to learn rust.