<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>xixixao</author><text>I&amp;#x27;m really impressed by the syntax. I have yet to find a piece of syntax I wouldn&amp;#x27;t like. Labelled arguments for example are delightful:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    pub fn replace(
      in string: String,
      each pattern: String,
      with replacement: String,
    ) {
      &amp;#x2F;&amp;#x2F; The variables `string`, `pattern`, and `replacement` are in scope here
    }

    replace(in: &amp;quot;A,B,C&amp;quot;, each: &amp;quot;,&amp;quot;, with: &amp;quot; &amp;quot;)&lt;/code&gt;&lt;/pre&gt;</text><parent_chain></parent_chain></comment><story><title>Gleam: a type safe language on the Erlang VM</title><url>https://gleam.run/</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>christophilus</author><text>Looks decent. I somehow missed the previous thousand discussions.&lt;p&gt;I’d love to hear from anyone running it in production.&lt;p&gt;I have always been BEAM-curious, but never felt comfortable running it in production, as it feels like a big black box, and I’m not confident that I’d be able to diagnose problems as readily as I can in .NET, Go, or Node. I’m not sure why I feel that way about BEAM.</text><parent_chain></parent_chain></comment><story><title>Gleam: a type safe language on the Erlang VM</title><url>https://gleam.run/</url></story>