<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>fao_</author><text>It&amp;#x27;s actually easier on the hands than using `_`. As on a standard (us, uk, chinese, etc.) keyboard underscore requires a shift-press whereas minus&amp;#x2F;hyphen requires a single press. It&amp;#x27;s a small change but you&amp;#x27;d be surprised how much of a difference it makes, given that tokens are a significant amount of all writing when programming.&lt;p&gt;Not to mention, in my opinion it&amp;#x27;s more aesthetically pleasing, but that&amp;#x27;s just me :)</text><parent_chain><item><author>mratsim</author><text>kebab-case? Is that even a thing?</text></item><item><author>weavie</author><text>Forgot to add.. in common lisp everything is kebab-cased which makes case a lot less significant. Not sure what happens in Nim?</text></item><item><author>weavie</author><text>Common lisp also ignores case (sort of..it&amp;#x27;s a little bit more complicated). I&amp;#x27;ve never found it to be a problem - apart from the compiler always uppercases my symbols when it reports to me, it feels a bit like being shouted at.</text></item><item><author>narimiran</author><text>&amp;gt; &lt;i&gt;I personally found it to be a turn-off.&lt;/i&gt;&lt;p&gt;I feel like this is mentioned (by the people who just glance over Nim) every time there is some discussion about Nim, and IMO it is blown way out of proportion.&lt;p&gt;In my cca year and half of using Nim, I not even &lt;i&gt;once&lt;/i&gt; had a problem with the style insensitivity.&lt;p&gt;IMO, you (general you) shouldn&amp;#x27;t use `my_foo` and `myFoo` for different things, regardless if a language allows for it or not.</text></item><item><author>aepiepaey</author><text>Last time I was going to try it, I got sidetracked reading up on rules for identifier equality, prompted by noticing that the nim package bundled its own grep (nimgrep).&lt;p&gt;Basically, Nim ignores case (except for the first character) and underscores in identifier names, so the following is a valid Nim program and all those names refer to the same variable:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    var myVar = 1
    my_var = 2
    mYVAR = 3
    echo(myVAR)
&lt;/code&gt;&lt;/pre&gt;
Most people wouldn&amp;#x27;t actually write code like that, but I personally found it to be a turn-off.&lt;p&gt;More on this: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;nim-lang.org&amp;#x2F;docs&amp;#x2F;manual.html#lexical-analysis-identifier-equality&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;nim-lang.org&amp;#x2F;docs&amp;#x2F;manual.html#lexical-analysis-ident...&lt;/a&gt;</text></item><item><author>rijoja</author><text>Even though I haven&amp;#x27;t taken it out for a spin just yet, I&amp;#x27;ve gotten a good impression of nim. Anybody out there who has tested that can say if my hunch is right or not?</text></item></parent_chain></comment><story><title>Advent of Nim</title><url>https://nim-lang.org/blog/2018/11/26/advent-of-nim.html</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>mhd</author><text>Not as common, as it clashes with using &amp;#x27;-&amp;#x27; for subtraction, but as that&amp;#x27;s never been a problem for Lisp, it&amp;#x27;s quite common there. Perl6 went that way, too, despite having infix syntax. But hey, it&amp;#x27;s Perl, we&amp;#x27;re used to syntactical warts.</text><parent_chain><item><author>mratsim</author><text>kebab-case? Is that even a thing?</text></item><item><author>weavie</author><text>Forgot to add.. in common lisp everything is kebab-cased which makes case a lot less significant. Not sure what happens in Nim?</text></item><item><author>weavie</author><text>Common lisp also ignores case (sort of..it&amp;#x27;s a little bit more complicated). I&amp;#x27;ve never found it to be a problem - apart from the compiler always uppercases my symbols when it reports to me, it feels a bit like being shouted at.</text></item><item><author>narimiran</author><text>&amp;gt; &lt;i&gt;I personally found it to be a turn-off.&lt;/i&gt;&lt;p&gt;I feel like this is mentioned (by the people who just glance over Nim) every time there is some discussion about Nim, and IMO it is blown way out of proportion.&lt;p&gt;In my cca year and half of using Nim, I not even &lt;i&gt;once&lt;/i&gt; had a problem with the style insensitivity.&lt;p&gt;IMO, you (general you) shouldn&amp;#x27;t use `my_foo` and `myFoo` for different things, regardless if a language allows for it or not.</text></item><item><author>aepiepaey</author><text>Last time I was going to try it, I got sidetracked reading up on rules for identifier equality, prompted by noticing that the nim package bundled its own grep (nimgrep).&lt;p&gt;Basically, Nim ignores case (except for the first character) and underscores in identifier names, so the following is a valid Nim program and all those names refer to the same variable:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    var myVar = 1
    my_var = 2
    mYVAR = 3
    echo(myVAR)
&lt;/code&gt;&lt;/pre&gt;
Most people wouldn&amp;#x27;t actually write code like that, but I personally found it to be a turn-off.&lt;p&gt;More on this: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;nim-lang.org&amp;#x2F;docs&amp;#x2F;manual.html#lexical-analysis-identifier-equality&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;nim-lang.org&amp;#x2F;docs&amp;#x2F;manual.html#lexical-analysis-ident...&lt;/a&gt;</text></item><item><author>rijoja</author><text>Even though I haven&amp;#x27;t taken it out for a spin just yet, I&amp;#x27;ve gotten a good impression of nim. Anybody out there who has tested that can say if my hunch is right or not?</text></item></parent_chain></comment><story><title>Advent of Nim</title><url>https://nim-lang.org/blog/2018/11/26/advent-of-nim.html</url></story>