saemei

Rust' memory safety feature includes "fearless concurrency".

Popular GC languages like Java or Go are not able to prevent a class of data race bugs that Rust prevents at compile time. Languages like Haskell of course handle it much better, but are for a multitude of reasons not popularly used in production.

And as the sibling comment points out, GC languages are not applicable everywhere. This discussion is in the context of the first not-C language being added to the Linux kernel. Can you imagine a GC language being similarly considered?

So yes, the borrow checker is amazing. That feeling of satisfaction and confidence when the program finally compiles after a round of serious coding or refactoring is unparalleled among the mainstream languages I've tried so far.

Sometimes ideologies actually point in the right direction. The hard part is to recognize the gems amid the firehose of truly bad ones.

FWIW, I think the memory safety-first ideology of Rust is worth spreading.

You can read the full talk here: https://calteches.library.caltech.edu/51/2/CargoCult.htm

> tasks that people either cannot currently do, or cannot easily do.

A todo entry or flipping lights via assistants also qualify as such tasks, if we broaden the definition of "easy". The flow from having the thought of an idea or a song to making a note or playing the song by just speaking out loud is just so convenient, without having to context switch from whatever one is doing. Controlling a set of IoT devices with custom commands is another good usecase.

Of course, not everyone has a workflow where a digital assistant fits well today. However, I expect that their usefulness will increase exponentially with time. We're surely heading to the sci-fi future where each house will have a personalized digital guardian responding to the wishes of the family, Jarvis style, no?