But finally it was time to sit down and do my own thing. Reading through The Book, I went through some of the tutorial projects, so I was a tad familiar in writing Rust code. We all know the difference between reading about something and actually doing it. I, too, recommend anyone interested in Rust to read it it is excellently written, updated regularly, and covers many non-Rust specific programming practices that any developer can benefit from. Additionally, a co-worker recommended that I read the Rust book ( The Book), which is exactly what I did. Though diving right into the project with docs by my side was enticing, Rust was just a bit too terse and foreign to wing it. However, I ended up using Elm to build the frontend, which I’ll expand more on later. I used Rust to cache file references and serve data to a desktop webview, which renders HTML and JavaScript. Hence, I decided to make a video management app that keeps track of video files across multiple external devices. The reason I wanted to give Rust a shot was to get a deeper understanding of lower-level computing my prior experiences involved a couple problem sets in C from cs50 and making a print server in Electron (a way to make cross-platform apps using JavaScript).įor me, the best way to learn any new language or paradigm is to do a side project. If you want to write your good ol’ CRUD app, you can. If you want to talk to your GPU, you can. What I like to interpret this as is that Rust allows you to write low-level programs at a high level. Rust is a programming language, moreover a “multi-paradigm system programming language”. However today I’ll be talking about this rust.
0 kommentar(er)
