AquilaFasciata

Note: Many libraries have NYT codes for 24-72hrs. Like the San Fransisco Public Library.

https://sfpl.libanswers.com/faq/166904

It's difficult to find one that pays $50-60,000.

No, they rely on "consultants."

Reminder that this is what the author said about safety: "it manages to combine speed and low-level control with a high level of bug-resistance, more commonly referred to as safety"

I'm a hobbiest, so I only write in it 4 times a week, but I only run into borrow checker issues when I refactor large portions of existing code.

> it manages to combine speed and low-level control with a high level of bug-resistance, more commonly referred to as safety.

This article didn't even make it 2 paragraphs before being incorrect. Safety isn't bug resistance - Safety is ensuring memory integrity. Bugs are still easy to write, they're just going to be logic bugs instead of use after frees, double frees, etc.

The first example of a function and access to fields misses point as well. If you just wanted to edit a field locally, you can do that without references. If you're sharing the struct around, then you don't want more than one mutable reference at a time anyway.

Yes. I learned Rust in a weekend. Basic Rust isn't that complicated, especially when you listen to the compiler's error messages (which are 42x as helpful compared with C++ compiler errors).