The main valid complaints in Dan&#x27;s post were:<p>1. Insufficient testing &amp; coverage. Code coverage is now at 84% of base Julia, from somewhere around 50% at the time he wrote this post. While you can always have more tests (and that is happening), I certainly don&#x27;t think that this is a major complaint at this point.<p>2. Package issues. Julia now has package precompilation so package loading is pretty fast. The package manager itself was rewritten to use libgit2, which has made it much faster, especially on Windows where shelling out is painfully slow.<p>3. Travis uptime. This is much better. There was a specific mystery issue going on when Dan wrote that post. That issue has been fixed. We also do Windows CI on AppVeyor these days.<p>4. Documentation of Julia internals. Given the quite comprehensive developer docs that now exist, it&#x27;s hard to consider this unaddressed:<p><a href="http:&#x2F;&#x2F;julia.readthedocs.org&#x2F;en&#x2F;latest&#x2F;devdocs&#x2F;julia&#x2F;" rel="nofollow">http:&#x2F;&#x2F;julia.readthedocs.org&#x2F;en&#x2F;latest&#x2F;devdocs&#x2F;julia&#x2F;</a><p>So the legitimate issues raised in that blog post are fixed.