From: *@eli.users.panix.com   
      
   In comp.misc, Ben Collver   wrote:   
   > That's why when I see that a project aims to "force" the use of or   
   > the switch from C to Rust, to the extent of my possibilities, I flee   
   > from it as if I were pursued by the Balrog of the Lord of the Rings   
   > with his whip.   
      
   You do you, but I generally let tool developers pick the language they   
   like for their tool and just use the output. (If I have to compile it   
   myself, the newer languages are a little more suspect because they tend   
   to be very picky about which version you compile with, but mostly I   
   don't compile myself, I use the packaged version.)   
      
   To me, the really problem with git, besides the god awful command line   
   usage, is the reliance on an unchanging scheme for commits, sha-1. A   
   more flexible system would allow switching to another scheme as   
   collision effort warrants.   
      
   Rust, C, Go, Pascal, Scheme, Lisp, or even C++ for the tool: who cares?   
      
   Elijah   
   ------   
   always had a softspot for Perforce, but not Perforce licensing   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)