<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>f1shy</author><text>I always saw C++ and Java addressing other issues, like low level memory management, and higher level abstractions like objects. Not so much type policy.
Anyways I see a strong tendency in lots of programmers dismissing anything that is not type static-strict-safe, and others advocating for a more relaxed system.</text><parent_chain><item><author>rollcat</author><text>It feels like we&amp;#x27;re going in cycles. C was somewhat lax with type checking, thus C++ and Java were both made more strict. Looking to escape the tyranny of static typing, the rise of Python, Ruby, or JavaScript instead left us with a desire that Rust, Go, and TypeScript now fulfill. I wonder what&amp;#x27;s the next step? LLMs are extremely broad in what they accept, but don&amp;#x27;t exactly fill the same niches.</text></item><item><author>appplication</author><text>&amp;gt; Maybe now I&amp;#x27;ll be able to actually figure out what data to send libraries without actually reading their source code.&lt;p&gt;One could hope, but any library abusing kwargs in all their methods is showing they’re willing to go through the absolute minimum to make their code usable, let alone readable and self-documenting.</text></item><item><author>dandiep</author><text>Ooh, seems there is a new syntax for declaring the types of kwargs [1]:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  from typing import TypedDict, Unpack
  
  class Movie(TypedDict):
    name: str
    year: int

  def foo(*kwargs: Unpack[Movie]): ...
&lt;/code&gt;&lt;/pre&gt;
Maybe now I&amp;#x27;ll be able to actually figure out what data to send libraries without actually reading their source code.&lt;p&gt;1. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.python.org&amp;#x2F;3.12&amp;#x2F;whatsnew&amp;#x2F;3.12.html#pep-692-using-typeddict-for-more-precise-kwargs-typing&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.python.org&amp;#x2F;3.12&amp;#x2F;whatsnew&amp;#x2F;3.12.html#pep-692-usin...&lt;/a&gt;</text></item></parent_chain></comment><story><title>Python 3.12</title><url>https://www.python.org/downloads/release/python-3120/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>tomrod</author><text>I&amp;#x27;m holding out hope for a Fortran resurgence.&lt;p&gt;It&amp;#x27;s a tiny hope. But a hope nonetheless. Fortran is fun.</text><parent_chain><item><author>rollcat</author><text>It feels like we&amp;#x27;re going in cycles. C was somewhat lax with type checking, thus C++ and Java were both made more strict. Looking to escape the tyranny of static typing, the rise of Python, Ruby, or JavaScript instead left us with a desire that Rust, Go, and TypeScript now fulfill. I wonder what&amp;#x27;s the next step? LLMs are extremely broad in what they accept, but don&amp;#x27;t exactly fill the same niches.</text></item><item><author>appplication</author><text>&amp;gt; Maybe now I&amp;#x27;ll be able to actually figure out what data to send libraries without actually reading their source code.&lt;p&gt;One could hope, but any library abusing kwargs in all their methods is showing they’re willing to go through the absolute minimum to make their code usable, let alone readable and self-documenting.</text></item><item><author>dandiep</author><text>Ooh, seems there is a new syntax for declaring the types of kwargs [1]:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  from typing import TypedDict, Unpack
  
  class Movie(TypedDict):
    name: str
    year: int

  def foo(*kwargs: Unpack[Movie]): ...
&lt;/code&gt;&lt;/pre&gt;
Maybe now I&amp;#x27;ll be able to actually figure out what data to send libraries without actually reading their source code.&lt;p&gt;1. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.python.org&amp;#x2F;3.12&amp;#x2F;whatsnew&amp;#x2F;3.12.html#pep-692-using-typeddict-for-more-precise-kwargs-typing&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.python.org&amp;#x2F;3.12&amp;#x2F;whatsnew&amp;#x2F;3.12.html#pep-692-usin...&lt;/a&gt;</text></item></parent_chain></comment><story><title>Python 3.12</title><url>https://www.python.org/downloads/release/python-3120/</url></story>