rust-for-rustaceans.com VS neovim

https://rust-for-rustaceans.com/ is meant to be a book for more advanced concepts.

RustForRustaceans has great in depth explainations of most (all?) Rust concepts. So I would pick this one once you're familiar with the basic concepts explained in thee book.

Another good piece, but I wouldn't say its for beginners, is Rust for Rustaceans by Jon Gjengset. Its definitely more intermediate topics than beginner. Still good to know about it ;)

Rust for Rusraceans

For a deeper dive into the language and stdlib, the Crust of Rust videos are great. Also, Jon's book Rust for Rustaceans is a good continuation when you've finished the official book.

Rust for rustaceons includes a decent explanation of how the whole thing works.

I love this honest, high-level take on the book. So much so that I put it in "what readers say" on rust-for-rustaceans.com. Hope you don't mind!

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.