{"id":35213,"date":"2005-06-23T09:01:03","date_gmt":"2005-06-23T09:01:03","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2005\/06\/23\/why-does-the-createprocess-function-do-autocorrection\/"},"modified":"2005-06-23T09:01:03","modified_gmt":"2005-06-23T09:01:03","slug":"why-does-the-createprocess-function-do-autocorrection","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20050623-03\/?p=35213","title":{"rendered":"Why does the CreateProcess function do autocorrection?"},"content":{"rendered":"<p>Programs that weren&#8217;t designed to handle long file names would make mistakes like taking the path to the executable and writing it into the registry, unaware that the path might contain a space that needs quoting. (Spaces&mdash;while technically legal&mdash;were extremely rare in SFN paths.) The CreateProcess function had to decide whether to &#8220;autocorrect&#8221; these invalid paths or to let those programs simply stop working.\n This is the battle between pragmatism and purity.\n Purity says, &#8220;Let them suffer for their mistake. We&#8217;re not going to sully our beautiful architecture to accomodate such stupidity.&#8221; Of course, such an attitude comes with a cost: People aren&#8217;t going to use your &#8220;pure&#8221; system  if it can&#8217;t run the programs that they require.\n Put another way, it doesn&#8217;t matter how great your 1.0 version is if you don&#8217;t survive long enough to make a 2.0.\n Your choice is between &#8220;being pure and unpopular&#8221; or &#8220;being pragmatic and popular&#8221;. Look at all the wonderful technologies that died for lack of popularity despite technical superiority. Sony Betamax. Mattel Intellivision. (And, in the United States: The metric system.)\n Electric cars are another example. As great as electric cars are, they never reached any significant market success. Only after conceding to popularity and &#8220;sullying&#8221; their &#8220;purity&#8221; by adding a gasoline hybrid engine did they finally gain acceptance.\n I see this happening over and over again. A product team that, hypothetically, makes automated diagramming software, says, &#8220;I can&#8217;t believe we&#8217;re losing to Z. Sure, Z&#8217;s diagrams may be fast and snazzy, but ours gets &lt;subtle detail&gt; right, and when you go to &lt;extreme case&gt; their diagrams come out a little distorted, and they&#8217;re faster only because they don&#8217;t try to prevent X and Y from overlapping each other in &lt;scenario&nbsp;Q&gt;. We&#8217;re doing all those things; that&#8217;s why we&#8217;re slower, but that&#8217;s also why we&#8217;re better. Those people over at Z just don&#8217;t &#8216;get it&#8217;.&#8221;<\/p>\n<p> Guess what. People are voting with their wallets, and right now their wallets are saying that Z is better in spite of all those &#8220;horrible flaws&#8221;. Whatever part of &#8220;it&#8221; they don&#8217;t get, it&#8217;s certainly not the &#8220;make lots of people so happy that they send you money&#8221; part. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Programs that weren&#8217;t designed to handle long file names would make mistakes like taking the path to the executable and writing it into the registry, unaware that the path might contain a space that needs quoting. (Spaces&mdash;while technically legal&mdash;were extremely rare in SFN paths.) The CreateProcess function had to decide whether to &#8220;autocorrect&#8221; these invalid [&hellip;]<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[2],"class_list":["post-35213","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-history"],"acf":[],"blog_post_summary":"<p>Programs that weren&#8217;t designed to handle long file names would make mistakes like taking the path to the executable and writing it into the registry, unaware that the path might contain a space that needs quoting. (Spaces&mdash;while technically legal&mdash;were extremely rare in SFN paths.) The CreateProcess function had to decide whether to &#8220;autocorrect&#8221; these invalid [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/35213","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=35213"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/35213\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=35213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=35213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=35213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}