Lup Yuen Lee 李立源 @lupyuen@qoto.org

@morenonatural @lupyuen I think that we agree that inheritance is bad and not flexible. Multiple dispatch is one solution, but Rust's traits are another solution which, at least in comparison to Julia's multiple dispatch, seems to be much more robust to me.

I hope that it is clear that I am not against Julia. Quite the opposite, I teach and push Julia and will continue to do so. I just find some of its promises misleading and for some cases, Rust is a much better fit.

@morenonatural @lupyuen You are right about "Julia written in Julia" being powerful! I did mention it in the post and I find it much better than the approach of Python for example with its C code. Julia makes reading and contributing to code much easier than Python.

Thanks for sharing the talk about multiple dispatch. I am already familiar with it and yes, multiple dispatch is fascinating, but it has its disadvantages at least in Julia because of the missing interfaces as mentioned in the post.

@morenonatural @lupyuen About the first point with linters or static analyzers of a dynamically typed language and why they will never reach the correctness and reliability of Rust: I did add an appendix for JET.jl which is a static analysis tool for Julia. It is an example of what I mean:

https://mo8it.com/blog/rust-vs-julia/#jet-jl

If you mean the borrow checker with the "questionable model for memory handling", then please question it. If you have any doubts about it, please share it with the community :D

@morenonatural

My bias; towards statically typed languages.

There are arguments on both sides, and the good thing is we don't have to unite behind one language for everything.

Rust is trying to solve a problem that humans can't handle; understanding what could possibly go wrong in multi-threaded applications. I don't think it is doing a great job at that (compared to Ponylang), but it is a lot better than C++.

@lupyuen