&gt; without a garbage collector, that&#x27;s the novel part?That&#x27;s not quite how it works in various languages. You appear to be thinking of the garbage collector as something inseparable from the language.Both Dlang and Vlang have optional garbage collectors, that can be turned off. In the case of Vlang, none of its libraries depend on the garbage collector. Vlang offers optional (flexible) memory management, somewhat similar to Nim (but they presently don&#x27;t have optional ownership).In the case of Julia and Vlang, their optional ownership is new and experimental. Dlang&#x27;s optional ownership has been around for some years now, showing that it could be done.Dlang and Vlang allow you to choose the type of memory management (along with some other languages) that you would like to use. Vlang does it by command line flags. You can turn off garbage collection and turn on ownership.

Yes, it&#x27;s a critical distinction that&#x27;s important in many systems domains, but getting some form of ownership policy and method - even if implemented with a GC I think is a step forward in terms of building reliable code.The thing about it being optional in some languages is that it&#x27;s an experiment, but one that as a feature it really pays off the more code in the ecosystem is compliant to ownership tracking. For rust, it&#x27;s the vast majority of it (with opt out explicitly findable..) For languages offering it optionally, it&#x27;s harder to assemble the full benefit.

&gt; Rust is becoming less special in this area. Languages such as Dlang, Vlang, and Julia have added optional ownership and borrowingIsn&#x27;t the crux that Rust does those things without a garbage collector, that&#x27;s the novel part? Someone correct me if I&#x27;m wrong (likely), but I think all those languages have garbage collectors, which Rust doesn&#x27;t.

I guarantee they&#x27;ll be complaining about unsafe rust in 10-15 years, mark my words. Just like they said exceptions &quot;force&quot; a programmer to deal with all error cases (newsflash, they still ignore it), rust will not eliminate memory errors.

Rust is becoming less special in this area. Languages such as Dlang, Vlang, and Julia have added optional ownership and borrowing. As these offerings are optional, many can see this as greater programmer freedom to decide what to use for their projects, with languages that are easier to use or read.

I am not familiar with scene graphs, but what is the problem with borrowing or refcounting? This article showed how you can have multiple mutable references in Rust, even multiple mutable references running in parallel threads.

This is all well and dandy for some usage scenarios but breaks in others, eg. scene graphs and GUI&#x27;s.A scene graph needs 2 mutable references, and has nothing to do with ownership. Same issue exists with GUI&#x27;s. The pattern that Rust forces is to always request a reference, which incurs a performance penalty while retrieving the same reference again and again and again.

Rust Memory Management: Ownership vs. Reference Counting