[Improved documentation seems mentioned repeatedly by you, so it does sound demanding. And Julia the project, JuliaLang, is great, that’s why I and many stick with it.]
I really can’t speak for all programmers or all packages, but I want to defend lazy programmers (to be fair, may not apply to docs though):
I’m lazy, and most great developers I know are lazy too.
I do like you bringing up stability (what I answered for Julia and the ecosystem, I’m not worried, it’s best-in-class with Julia). Since it’s already answered (according to the title) I suppose we/you could lock/solve the thread. Documentation part of it could be split out, or just not. I don’t think much further discussion on it is warranted either.
I would like to point out one thing though. It’s not a project. Julia[Lang] is one, each package is another (and statistics is actually being split from Julia), or at least some of them can be grouped into ecosystems, e.g. SciML is one of 100+ packages. WHile I know many individual packages, there’s no way for me or anyone to defend all packagesor all the ecosystems of packages (except the developers themselves).
As much as I like and use Julia for statistics (to compete with e.g. R/CRAN), I and others might not use Julia for stuff related to it or even data science.
There are at least 4 types:
To be fair, some doc types belong with the code, some like tutorials do not, and (physical) books need to be elsewhere. It’s practical to a degree to link to docs, but not all of it, and you might be ignorant of some of the docs, blogs or books (stuff people DO get paid for).
I don’t know of a single Julia package that’s not stable since supporting Julia 1.0, and all will continue to be. [And by that I mean pure Julia code having nothing to do with other languages. I know of three exceptions, Cxx.jl (to call C++, for obscure reasons, used non-public API, CppWrap.jl still works to call C++). At some point JavaCall.jl had some issues, I believe solved now. The third exception was Genie.jl, it used a non-public API, now fixed. Was mainly a problem for the developer, not users.]
So Cxx.jl is the only package I can think of not working in currently supported Julia, but even then it works in older Julia (1.3). Same applies to all pre-1.0 Julia code. I don’t think the situation can be better. You are always going to have problem in some cases with unmaintained “bitrotted” code, so choosing the best package for the future is important. But we can’t predict the future very well, and as I explained even bitrotten code will keep working.
I suggest you should use Makie.jl, that seems to be the future, and best plotting package. Gadfly.jl:
is based largely on Hadley Wickhams’s ggplot2 for R and Leland Wilkinson’s book The Grammar of Graphics.
It seems maintained too, consider though:
I don’t know much about it, except that it seems like a competing package, and it’s built on Makie.jl,
I didn’t understand “there is holes places” (feel free to direct message me, even email, I just advice emailing shouldn’t be implied to be ok [regarding docs]).