XPost: comp.theory   
   From: 643-408-1753@kylheku.com   
      
   On 2025-11-27, olcott  wrote:   
   > On 11/26/2025 10:48 PM, Mike Terry wrote:   
   >> On 27/11/2025 04:19, Kaz Kylheku wrote:   
   >>> On 2025-11-27, olcott  wrote:   
   >>>> The chief editor of one of the most prestigious   
   >>>> computer science journals exchanged about 15   
   >>>> emails with me. The bottom line was that he   
   >>>> could not understand the x86 language well enough.   
   >>>   
   >>> LOL; the obvious interpretation of that is "I will say anything   
   >>> for you to stop e-mailing me, you sick crank".   
   >>>   
   >>   
   >> Or... the chief editor really was ignorant of the x86 instruction set!   
   >> Yes, you'd think that someone in his role would have an idea about how   
   >> processors work (executing instructions, and all that stuff) and have   
   >> some familiarity with x86, but apparently not!   
   >>   
   >> But don't worry - PO is in the process of making a C-interpreter version   
   >> of his argument.  Then the editor will have no problem understanding   
   >> PO's argument - you just wait and see!   
   >>   
   >> Or will he?  If the chief editor is an ignorant dumbo   
   >   
   > Then he wouldn't have been the chief editor of   
   > one of the most prestigious computer science   
   > journals that exist.   
   >   
   >> who's baffled by   
   >> x86, who's to say he won't be equally ignorant of "C"?  In fact, I'll   
   >> bet that's how it will turn out when PO submits is new revised paper.   
   >> [From PO's perspective at least.]  Hehe.   
   >>   
   >   
   > The key thing about C is that it is simple   
   > enough that cheaters look ridiculous.   
      
   You will never be taken seriously if you use languages that are   
   completely out of favor in CS academia for doing research in this kind   
   of topic.   
      
   You need a language in which a meta-circular interpreter   
   (interpreter for that language written in that langauge)   
   is about a page of code.   
      
   Also, you  must work in a purely functional language   
   in which impure functions are /inexpressible/. That way   
   everyone knows at a glance that your results are not   
   incorrect on account of some hidden impurity.   
      
   Or else, you must laboriously work everything out with   
   Turing Machines: like strip mining for coal with a spoon.   
      
   --   
   TXR Programming Language: http://nongnu.org/txr   
   Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal   
   Mastodon: @Kazinator@mstdn.ca   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)