<story><title>Rust&apos;s 2018 roadmap</title><url>https://blog.rust-lang.org/2018/03/12/roadmap.html</url></story><parent_chain><item><author>golergka</author><text>&amp;gt; let hello = String::from(&amp;quot;שָׁלוֹם&amp;quot;);&lt;p&gt;This brings back PTSD for anyone who implemented ad-hoc RTL and UTF-16 surrogate pairs support in an environment that lacked them. Thank g-d I insisted that we at least omit diacritics as nobody uses them and they&amp;#x27;re a huge pain to implement and QA properly.&lt;p&gt;Also, can we please, please, please keep source code files as pure ascii? Asking as a non-native english speaker. There&amp;#x27;re a lot of tools that we developers need to use on those, and their encoding issues tend to follow the Murphy&amp;#x27;s law and appear at the most inconvenient moment.&lt;p&gt;Edit regarding localization: all projects that I&amp;#x27;ve worked on had localization in separate json or XML files, with automatic import&amp;#x2F;export from spreadsheets that would be filled by third party localization company.&lt;p&gt;This is the line of code I find my cursor on literally the moment I switch to HN:&lt;p&gt;questIcon.Text.text = (&amp;quot;Quest:&amp;quot; + World.current[index].template.trueId + &amp;quot;_title&amp;quot;).T();&lt;p&gt;Where T() is the extension method from localization system. Why on earth would you include user-facing strings in the code itself?</text></item><item><author>cpach</author><text>&lt;p&gt;&lt;pre&gt;&lt;code&gt;  let hello = String::from(&amp;quot;السلام عليكم&amp;quot;);
  let hello = String::from(&amp;quot;Dobrý den&amp;quot;);
  let hello = String::from(&amp;quot;Hello&amp;quot;);
  let hello = String::from(&amp;quot;שָׁלוֹם&amp;quot;);
  let hello = String::from(&amp;quot;नमस्ते&amp;quot;);
  let hello = String::from(&amp;quot;こんにちは&amp;quot;);
  let hello = String::from(&amp;quot;안녕하세요&amp;quot;);
  let hello = String::from(&amp;quot;你好&amp;quot;);
  let hello = String::from(&amp;quot;Olá&amp;quot;);
  let hello = String::from(&amp;quot;Здравствуйте&amp;quot;);
  let hello = String::from(&amp;quot;Hola&amp;quot;);
&lt;/code&gt;&lt;/pre&gt;
This is such a beautiful sight for anyone who remembers the bad old days of Extended ASCII.</text></item><item><author>smoe</author><text>I started learning Rust over the weekends and I think the second edition &amp;quot;The Rust Programming Language&amp;quot; is among the best introductory books on a programming language I have read (well half way so far).&lt;p&gt;As someone not only new to Rust but also systems programming in general I especially appreciate that the chapters include actual reasoning about why things are how they are in Rust and that they seem pretty open about drawbacks of the choices. As well as the use of precise language instead of trying to be too cute and overly beginner friendly.&lt;p&gt;An example for this is the lengthy page on Strings:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;doc.rust-lang.org&amp;#x2F;book&amp;#x2F;second-edition&amp;#x2F;ch08-02-strings.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;doc.rust-lang.org&amp;#x2F;book&amp;#x2F;second-edition&amp;#x2F;ch08-02-string...&lt;/a&gt;&lt;p&gt;It really makes me feel you want me to understand what I&amp;#x27;m doing from the start instead of getting a generic app out of the door as quick as possible and then tediously figure out the next basic steps from screencasts, scattered blog posts etc.&lt;p&gt;Also big plus for having the book and api doc available offline by default!&lt;p&gt;I&amp;#x27;m going to try to come by #rustdoc and see if there something I could contribute.</text></item></parent_chain><comment><author>lucideer</author><text>&amp;gt; &lt;i&gt;can we please, please, please keep source code files as pure ascii? Asking as a non-native english speaker. There&amp;#x27;re a lot of tools&lt;/i&gt;&lt;p&gt;If there are tools that break when this happens, those tools need to be fixed. Bugs in those tools need to be found (through usage) and reported. If we avoid the problem by strictly sticking to ascii in source files, that amounts to sweeping those bugs under the carpet.&lt;p&gt;Furthermore, another commenter said &amp;quot;use good tools&amp;quot;. The inverse of this—don&amp;#x27;t use bad tools—is important: developing tools that correctly handle encoding issues needs to be seen by developers as a priority. There needs to be a ramification (in the form of bug reports, complaints, etc.) if encoding issues are not considered by tool makers.</text></comment>
<story><title>Rust&apos;s 2018 roadmap</title><url>https://blog.rust-lang.org/2018/03/12/roadmap.html</url></story><parent_chain><item><author>golergka</author><text>&amp;gt; let hello = String::from(&amp;quot;שָׁלוֹם&amp;quot;);&lt;p&gt;This brings back PTSD for anyone who implemented ad-hoc RTL and UTF-16 surrogate pairs support in an environment that lacked them. Thank g-d I insisted that we at least omit diacritics as nobody uses them and they&amp;#x27;re a huge pain to implement and QA properly.&lt;p&gt;Also, can we please, please, please keep source code files as pure ascii? Asking as a non-native english speaker. There&amp;#x27;re a lot of tools that we developers need to use on those, and their encoding issues tend to follow the Murphy&amp;#x27;s law and appear at the most inconvenient moment.&lt;p&gt;Edit regarding localization: all projects that I&amp;#x27;ve worked on had localization in separate json or XML files, with automatic import&amp;#x2F;export from spreadsheets that would be filled by third party localization company.&lt;p&gt;This is the line of code I find my cursor on literally the moment I switch to HN:&lt;p&gt;questIcon.Text.text = (&amp;quot;Quest:&amp;quot; + World.current[index].template.trueId + &amp;quot;_title&amp;quot;).T();&lt;p&gt;Where T() is the extension method from localization system. Why on earth would you include user-facing strings in the code itself?</text></item><item><author>cpach</author><text>&lt;p&gt;&lt;pre&gt;&lt;code&gt;  let hello = String::from(&amp;quot;السلام عليكم&amp;quot;);
  let hello = String::from(&amp;quot;Dobrý den&amp;quot;);
  let hello = String::from(&amp;quot;Hello&amp;quot;);
  let hello = String::from(&amp;quot;שָׁלוֹם&amp;quot;);
  let hello = String::from(&amp;quot;नमस्ते&amp;quot;);
  let hello = String::from(&amp;quot;こんにちは&amp;quot;);
  let hello = String::from(&amp;quot;안녕하세요&amp;quot;);
  let hello = String::from(&amp;quot;你好&amp;quot;);
  let hello = String::from(&amp;quot;Olá&amp;quot;);
  let hello = String::from(&amp;quot;Здравствуйте&amp;quot;);
  let hello = String::from(&amp;quot;Hola&amp;quot;);
&lt;/code&gt;&lt;/pre&gt;
This is such a beautiful sight for anyone who remembers the bad old days of Extended ASCII.</text></item><item><author>smoe</author><text>I started learning Rust over the weekends and I think the second edition &amp;quot;The Rust Programming Language&amp;quot; is among the best introductory books on a programming language I have read (well half way so far).&lt;p&gt;As someone not only new to Rust but also systems programming in general I especially appreciate that the chapters include actual reasoning about why things are how they are in Rust and that they seem pretty open about drawbacks of the choices. As well as the use of precise language instead of trying to be too cute and overly beginner friendly.&lt;p&gt;An example for this is the lengthy page on Strings:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;doc.rust-lang.org&amp;#x2F;book&amp;#x2F;second-edition&amp;#x2F;ch08-02-strings.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;doc.rust-lang.org&amp;#x2F;book&amp;#x2F;second-edition&amp;#x2F;ch08-02-string...&lt;/a&gt;&lt;p&gt;It really makes me feel you want me to understand what I&amp;#x27;m doing from the start instead of getting a generic app out of the door as quick as possible and then tediously figure out the next basic steps from screencasts, scattered blog posts etc.&lt;p&gt;Also big plus for having the book and api doc available offline by default!&lt;p&gt;I&amp;#x27;m going to try to come by #rustdoc and see if there something I could contribute.</text></item></parent_chain><comment><author>pleasecalllater</author><text>&amp;gt; Also, can we please, please, please keep source code files as pure ascii? Asking as a non-native english speaker.&lt;p&gt;I&amp;#x27;m a non native English speaker. That&amp;#x27;s why I hate tools, and websites which don&amp;#x27;t understand that people have different letters in names. Just use good tools.</text></comment>