@saxnot thread seems broken on my end, I blame @jmw150, but anyway, sure, frees their mind, as in instead of studying the problem domain and designing a solution, they have to study the borrow checker implementation and work around it. Did you know you can't write a doubly linked list in safe rust? One has to wonder what other known and unknown entirely safe data structures, that might be the perfect fit for one's use case, one can not write, when one's mind is so free of memory trouble. Oh yes I too love not thinking about essential design elements of the system I'm working on, that's "how big/complex highly multithreaded project with a big dev team" should work, by not thinking. We don't want to have to teach the stupid interns our practices, we just want to unleash a dozen of them on the codebase and while they are wrecking absolute havoc, rely on the tooling to make sure the havoc is not of the particular kind that the latest pop culture buzz is all about. Why are we so careless you might ask, well, because there is no practice to teach, this is how our whole project was built from ground up, and this is how the whole industry works - end users are a commodity ripe for exploitation, quality standards don't exist, pretense and marketing alone sells imaginary products, errors are just a natural phenomenon that nobody is accountable for, THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

@TheAlgorythm @schnedan@kif.rocks @jmw150