<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>GolDDranks</author><text>Excellent post, thank you!&lt;p&gt;By the way, I&amp;#x27;ve sometimes heard that it was the popularity of emoji that finally made American and Western European coders learn about the particulars of unicode. Is this just a jokingly told anecdote, or did emoji really help?</text><parent_chain></parent_chain></comment><story><title>Let’s Stop Ascribing Meaning to Code Points</title><url>https://manishearth.github.io/blog/2017/01/14/stop-ascribing-meaning-to-unicode-code-points/</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>scrollaway</author><text>Excellent post.&lt;p&gt;&amp;gt; &lt;i&gt;Now, Rust is a systems programming language and it just wouldn’t do to have expensive grapheme segmentation operations all over your string defaults. I’m very happy that the expensive O(n) operations are all only possible with explicit acknowledgement of the cost. So I do think that going the Swift route would be counterproductive for Rust.&lt;/i&gt;&lt;p&gt;I&amp;#x27;m not sure I understand the logic here. How is Rust exempt but not, say, Python? Just because it&amp;#x27;s a systems language? I get why you wouldn&amp;#x27;t make it the default in Rust, but the logic applies to all languages, doesn&amp;#x27;t it?&lt;p&gt;Aside: I was talking about this with a friend just yesterday. Is there any language that separates the concept of a string and a user-facing string? Specifically for localization purposes, the way gettext works.&lt;p&gt;eg. I wish that in Python you could do this:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    err = &amp;quot;internal_error&amp;quot;
    msg = t&amp;quot;Internal error!&amp;quot;
&lt;/code&gt;&lt;/pre&gt;
error_msg would be easy to pick up for translation, rather than have to do some cludgy import as _ and _(&amp;quot;Internal error!&amp;quot;). Hm, now that I&amp;#x27;m writing this here, I guess it&amp;#x27;s still not a type you&amp;#x27;d want to operate differently on than just plain unicode strings.</text><parent_chain></parent_chain></comment><story><title>Let’s Stop Ascribing Meaning to Code Points</title><url>https://manishearth.github.io/blog/2017/01/14/stop-ascribing-meaning-to-unicode-code-points/</url></story>