JavaScript is literally the worst language, yet people make large products out of it; so if it’s possible to make production code with JavaScript, then it must be possible to make production code with Julia. There might be lessons to be learned—especially w.r.t. tooling, e.g. linting.
I feel this. It seems related to the Lisp curse.
Ecosystem fragmentation, outdated and incomplete package documentation, and poor method discoverability can make it pretty rough when you’re trying to explore the design space and learn new APIs.
. Not much point in proving correctness of code that doesn’t correctly encode the author’s intent, which is hard to get right if it’s an illegible mess.
Even in the strictest language you can make bugs. Question is, what features will minimize the total errors, not just the errors that can be caught by the compiler? IMO Julia has found a pretty sweet spot here. (although maybe it can get sweeter?)