4 ms·

The title of the repo is spells "interpreter" correctly, so this submission's title should be fixed.

• cespare 12y ago
  Similarly it spells "Go" correctly :)
  • CatDevURandom 12y ago
    tl;dr - I'm upset because the raison d'etat for Go's name doesn't exist. Correct, no -- practical, probably. No matter how many gophers swear that {searchterm} + go returns just as good of results as {searchterm}+golang, it just isn't true. Maybe I'm just bitter because the reason Go was named Go was because -- and obviously I'm paraphrasing here... "we thought Oogle would be a really cool name for a debugger." Years later, here I am stuck searching {some search term} + GOLANG and step debugging with GDB. The worst part though is hearing people tell me, "Oh you know what, I realize how powerful printline statements and unit tests are for debugging! I don't even miss a debugger!" Or-- "have you tried GDB? Go Supports GDB! I haven't used it -- but it exists!" GDB is a god damn hate machine. And the chorus of "print statements are good enough" is motivated reasoning at its finest.
    • SixSigma 12y ago
      The debugger on plan9, acid, is a work of art.
      • f2f 12y ago
        similarly, mdb on solaris is very powerful.
• dang 12y ago
  Fixed.