I think the real reason is that Chris Lattner doesn’t want to work on Julia. He’s likely very (and justifiably so) opinionated about these topics, and probably wants a certain degree of creative authority over his projects.
Although from the way some Modular videos are done, it seems nowadays he is more in an overseer role and setting up the direction, while others are the ones actually pushing Mojo and Max tooling forward.
Maybe I just misunderstand it from the presentation format.
He works on Mojo a lot, mostly on weekends. In the past few months, he has worked on strings, collection literals, dependent types, reference captures,
comprehensions, and many other nice language features.
This is exactly my thought. Be it pen and paper or digital, writing out what your software needs to do and how it will do it saves an immense amount of time debugging or throwing things at the wall. I’m shocked at some of the responses here; there is a qualitative difference in the development experience when you spend the time designing (I also frequently do this by hand, but it doesn’t have to be) before implementing anything vs. opening an IDE and hammering something out.
I’d go further to say that software development isn’t about writing code, it’s about designing and understanding programs. Code is an implementation detail, the understanding is what is crucial.
