<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>susam</author><text>I am hoping this appears at &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;pubs.opengroup.org&amp;#x2F;onlinepubs&amp;#x2F;9699919799&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;pubs.opengroup.org&amp;#x2F;onlinepubs&amp;#x2F;9699919799&amp;#x2F;&lt;/a&gt; soon.  This is the link I use most often to go through the specification.  In fact, I owe a lot of my shell scripting skills to this online resource.&lt;p&gt;As a specific example, the seemingly simple matter of when the shell decides to split a string based on $IFS and when it does not were quite confusing to me until I went through the specification here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;pubs.opengroup.org&amp;#x2F;onlinepubs&amp;#x2F;9699919799&amp;#x2F;utilities&amp;#x2F;V3_chap02.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;pubs.opengroup.org&amp;#x2F;onlinepubs&amp;#x2F;9699919799&amp;#x2F;utilities&amp;#x2F;V...&lt;/a&gt;&lt;p&gt;For example, if&lt;p&gt;&lt;pre&gt;&lt;code&gt;  a=&amp;quot;foo bar&amp;quot;
&lt;/code&gt;&lt;/pre&gt;
then&lt;p&gt;&lt;pre&gt;&lt;code&gt;  ls $a
&lt;/code&gt;&lt;/pre&gt;
will split the value into two fields (thus two arguments to ls).  Of course we should surround $a with double-quotes to avoid the field splitting.  However the following is fine:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  case $a in
&lt;/code&gt;&lt;/pre&gt;
No field splitting occurs here.  However, to be kind to your code reviewer, you might want to double-quote this anyway for the sake of simplicity and consistency.  Behaviour like this is specified in sections &amp;quot;Field Splitting&amp;quot; and &amp;quot;Case Conditional Construct&amp;quot; of the aforementioned link.  Specification documents like this were formative in in my journey toward learning to write shell scripts confidently.</text><parent_chain></parent_chain></comment><story><title>Posix.1-2024 is published</title><url>https://ieeexplore.ieee.org/document/10555529</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>dveeden2</author><text>Where is POSIX actually useful today?&lt;p&gt;Is it mostly for shell scripts? Aren&amp;#x27;t people targetting bash or basic bourne shell features intead of posix? Is shellcheck checking for best practices instead of POSIX compliance?&lt;p&gt;And for other applications (GUI, servers, etc) strict POSIX compliance might be too restrictive?&lt;p&gt;And with many things being Linux (or Linux-like like WSL) the need for this might be less?&lt;p&gt;Are Android and&amp;#x2F;or iOS fully POSIX compliant?&lt;p&gt;Any good blog or presentation describing the current state of POSIX?</text><parent_chain></parent_chain></comment><story><title>Posix.1-2024 is published</title><url>https://ieeexplore.ieee.org/document/10555529</url></story>