<story><title>My favorite things that are coming with Julia 1.0</title><url>https://white.ucc.asn.au/2018/06/01/Julia-Favourite-New-Things.html</url></story><parent_chain></parent_chain><comment><author>ScottPJones</author><text>The creators of Julia have been focusing on technical, numerical, scientific computing first, however, the language was always intended to also be a good general purpose programming language (which it is) [I was lucky enough to attend Jeff Bezanson&amp;#x27;s Ph.D. thesis defense at M.I.T. 3 years ago - and was able to ask him that question there].
I used to be a full-time C&amp;#x2F;C++ programmer, focused on performance of large systems, however, since learning Julia I haven&amp;#x27;t had to go back to writing C or C++ even once in over 3 years, since I can write even the sort of low-level code I typically do in Julia, faster and easier than in other languages, and get the same performance.</text></comment>
<story><title>My favorite things that are coming with Julia 1.0</title><url>https://white.ucc.asn.au/2018/06/01/Julia-Favourite-New-Things.html</url></story><parent_chain></parent_chain><comment><author>twic</author><text>&amp;gt; It will be interesting to see exactly how &lt;i&gt;nothing&lt;/i&gt; and &lt;i&gt;missing&lt;/i&gt; play out in-practice. I feel like if all things go well, then in most circumstances operating with a &lt;i&gt;missing&lt;/i&gt; should return a missing (i.e. properation), and operating with a &lt;i&gt;nothing&lt;/i&gt; should throw an error (Much like a NullReferenceError).&lt;p&gt;We all know that having a null value in your language is a mistake, but i have to admit that it had not occurred to me that the fix was to have &lt;i&gt;two&lt;/i&gt; null values.</text></comment>