<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>ealexhudson</author><text>I wish they did &amp;quot;User Files&amp;quot; instead of &amp;quot;Users&amp;quot; too, because so much software breaks on the home area having a space in it.&lt;p&gt;Not least, it makes writing scripts for various shells and getting the quoting rules right an absolute pain as well...</text><parent_chain><item><author>alpaca128</author><text>Seems like MS had the same idea according to an answer in  the link:&lt;p&gt;&lt;i&gt;&amp;gt; Microsoft intentionally made programs install to C:\Program Files on Windows 95+ to force programmers to deal with spaces in filenames.&lt;/i&gt;</text></item><item><author>pimterry</author><text>I work on a complex desktop application, and it&amp;#x27;s been astounding the number of bugs that have appeared over the years triggered by spaces and other unusual characters in file names. If you do anything with subprocesses or path processing, it&amp;#x27;s absurdly easy to hit in a thousand different ways, over and over again.&lt;p&gt;Pro tip: rename your development directory (or even better: the workspace path in CI) to put a space and&amp;#x2F;or special characters in it.&lt;p&gt;Forces you to deal with this properly, and immediately ensures that every automated test checks this case without you having to remember every time. Hasn&amp;#x27;t been particularly inconvenient, since I&amp;#x27;m autocompleting it 99% of the time anyway, and I haven&amp;#x27;t shipped a single path parsing bug since.</text></item></parent_chain></comment><story><title>I&apos;m “still afraid to use spaces in file names” years old</title><url>https://twitter.com/TheIdOfAlan/status/1458117496087748618</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>323</author><text>Laughs in C:\PROGRA~1\ (try it, still works in Windows 10)</text><parent_chain><item><author>alpaca128</author><text>Seems like MS had the same idea according to an answer in  the link:&lt;p&gt;&lt;i&gt;&amp;gt; Microsoft intentionally made programs install to C:\Program Files on Windows 95+ to force programmers to deal with spaces in filenames.&lt;/i&gt;</text></item><item><author>pimterry</author><text>I work on a complex desktop application, and it&amp;#x27;s been astounding the number of bugs that have appeared over the years triggered by spaces and other unusual characters in file names. If you do anything with subprocesses or path processing, it&amp;#x27;s absurdly easy to hit in a thousand different ways, over and over again.&lt;p&gt;Pro tip: rename your development directory (or even better: the workspace path in CI) to put a space and&amp;#x2F;or special characters in it.&lt;p&gt;Forces you to deal with this properly, and immediately ensures that every automated test checks this case without you having to remember every time. Hasn&amp;#x27;t been particularly inconvenient, since I&amp;#x27;m autocompleting it 99% of the time anyway, and I haven&amp;#x27;t shipped a single path parsing bug since.</text></item></parent_chain></comment><story><title>I&apos;m “still afraid to use spaces in file names” years old</title><url>https://twitter.com/TheIdOfAlan/status/1458117496087748618</url></story>