4 ms·

> Although at first, some unfamiliar design decisions annoyed me, for they were not well explained in the tutorials I was learning the language from – e.g `arg:

> Although at first, some unfamiliar design decisions annoyed me, for they were not well explained in the tutorials I was learning the language from – e.g `arg: value` as a shortcut for `[{:arg, value}]` in function arguments and other places This complaint and a similar one for maps were the primary driver in me making an "Elixir tips" playlist of YT videos: https://www.youtube.com/watch?v=7w98voHko20&list=PLFhQVxlaKQEmO3gaork2WD5AY51LH3Ls0&index=13 https://www.youtube.com/watch?v=7w98voHko20&list=PLFhQVxlaKQ... What kinds of things have you been coding or reading in your Rust learning so far? I'm a pretty big fan of Herbert Wolverson's Pragprog Rust book and open source Roguelike project, as well as Tim McNamara's Rust in Action (which I've only gone through part of due to how each project leaves you wanting to keep building it after the book moves on to another).

plainOldText 4y ago
I wish I had this when I learned the language. :) I'll take a look, as your playlist is quite comprehensive it appears. Thanks for sharing! Re: Rust - I've been trying out basic examples, simple web servers, etc; nothing too fancy. But it just seems too ceremonious to get even the most basic things done. I own the book "Rust in Action", I just didn't have the proper time to go over it.
- AlchemistCamp 4y ago
  It takes you through the heavy lifting of writing a CHIP-8 emulator, a database and a whole bunch of things. It really feels like it could have been several books and he just had to cut back the scope of each part to fit everything in and ship it. The great thing about that is that it leaves you with projects just begging for you to dot the "i"s and cross the "t"s.