<story><title>Rust 1.32 released</title><url>https://blog.rust-lang.org/2019/01/17/Rust-1.32.0.html</url></story><parent_chain><item><author>KeyboardFire</author><text>It&amp;#x27;s funny that this is the first time I&amp;#x27;ve seen a language explicitly condone &amp;quot;print debugging.&amp;quot; It&amp;#x27;s one of those things that everyone says you&amp;#x27;re not supposed to do and then does anyway.&lt;p&gt;Does any other language have a similar feature?</text></item></parent_chain><comment><author>root_axis</author><text>I think debuggers are not worth the cost for many kinds of debugging scenarios. They&amp;#x27;re great for stepping through projects you&amp;#x27;re not really familiar with or in situations where code seems to be in violation of baseline expectations, but fiddling around with breakpoints and watches and other UI particularities of the debugger carries more cognitive overhead than &amp;quot;print debugging&amp;quot;. Additionally, I think the problem is better solved by using thoughtful and contextualized logging with appropriate severity levels. Couple this with a TDD approach to development and you&amp;#x27;ll end up in a workflow that is just &lt;i&gt;faster&lt;/i&gt; than stepping through lines of code when you could have your assumptions verified through logs and test assertions.</text></comment>
<story><title>Rust 1.32 released</title><url>https://blog.rust-lang.org/2019/01/17/Rust-1.32.0.html</url></story><parent_chain><item><author>KeyboardFire</author><text>It&amp;#x27;s funny that this is the first time I&amp;#x27;ve seen a language explicitly condone &amp;quot;print debugging.&amp;quot; It&amp;#x27;s one of those things that everyone says you&amp;#x27;re not supposed to do and then does anyway.&lt;p&gt;Does any other language have a similar feature?</text></item></parent_chain><comment><author>FartyMcFarter</author><text>This &amp;quot;print debugging is bad&amp;quot; idea never made sense. Debugging is largely an effort to understand what&amp;#x27;s going on inside a program - having the program &amp;quot;talk back&amp;quot; to you via prints can be a great way to do this.&lt;p&gt;Sometimes, print debugging is the only practical way to fix a bug. For example, very rare bugs which can only be reproduced by running many instances of the code for a long time, or situations where attaching a debugger is not feasible (as in live services).</text></comment>