<story><title>Deno 1.22</title><url>https://deno.com/blog/v1.22</url></story><parent_chain></parent_chain><comment><author>lucacasonato</author><text>Just to preemptively clear up some confusion: Deno is *not* removing type-checking.&lt;p&gt;The only change is that type checking is now it&amp;#x27;s own subcommand: `deno check`, instead of happening as part of `deno run`.&lt;p&gt;See last releases&amp;#x27; blog post for the rationale: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;deno.com&amp;#x2F;blog&amp;#x2F;v1.21#deno-check-and-the-path-to-not-type-checking-by-default&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;deno.com&amp;#x2F;blog&amp;#x2F;v1.21#deno-check-and-the-path-to-not-t...&lt;/a&gt;</text></comment>
<story><title>Deno 1.22</title><url>https://deno.com/blog/v1.22</url></story><parent_chain></parent_chain><comment><author>msoad</author><text>Deno getting out of type-checking for the most part is a good thing. Most projects depend on CI for production type checking and editor for local type checking.&lt;p&gt;I also love how Deno is nicely maturing. Can&amp;#x27;t wait to find a problem to solve with Deno!</text></comment>