<story><title>Nim in 2020: A Short Recap</title><url>https://nim-lang.org/blog/2020/12/28/nim-in-2020-a-short-recap.html</url></story><parent_chain></parent_chain><comment><author>zubspace</author><text>I&amp;#x27;ve used Nin for this years advent-of-code challenge. Never used Nim before  but there are some great tutorials [1].&lt;p&gt;It&amp;#x27;s a nice language with a great standard library. Implicit static typing is great after a bit of getting used to. Some things like tuples or &amp;quot;Object Variants&amp;quot; are fun to use.&lt;p&gt;The only thing I&amp;#x27;m missing is strong debugging support. You can use GDB and there is even some basic support for debugging in VSCode (through gdb behind the scenes). But most of the time I had to fall back to simple &amp;quot;echo&amp;quot; debugging because names were sometimes mangled, variables were not displayed or lines in nim did not correspond with lines in the final output, making debugging a chore. Unfortunately someone once started to write an embedded debugger (ENDB) for all platforms, but development stopped.&lt;p&gt;What&amp;#x27;s your opinion on this? In some way I would love to use Nim more in the future, but I&amp;#x27;m afraid, that the larger the codebase gets, the more I&amp;#x27;d suffer just because of debugging...&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;nim-lang.org&amp;#x2F;docs&amp;#x2F;tut1.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;nim-lang.org&amp;#x2F;docs&amp;#x2F;tut1.html&lt;/a&gt;</text></comment>
<story><title>Nim in 2020: A Short Recap</title><url>https://nim-lang.org/blog/2020/12/28/nim-in-2020-a-short-recap.html</url></story><parent_chain></parent_chain><comment><author>rattray</author><text>Wow, 35% growth in the package ecosystem is a great sign!</text></comment>