{"@attributes":{"version":"2.0"},"channel":{"title":"Tanay Gupta","link":"https:\/\/tanayg.com\/","description":"Recent content on Tanay Gupta","generator":"Hugo -- 0.161.1","language":"en-us","lastBuildDate":"Sat, 19 Oct 2024 18:44:16 +0530","item":[{"title":"On token boundaries","link":"https:\/\/tanayg.com\/blog\/on-token-boundaries\/","pubDate":"Sat, 19 Oct 2024 18:44:16 +0530","guid":"https:\/\/tanayg.com\/blog\/on-token-boundaries\/","description":"And the implicit price we pay for them"},{"title":"An extraordinary code editor - LibreOffice Calc","link":"https:\/\/tanayg.com\/blog\/an-extraordinary-code-editor-libreoffice-calc\/","pubDate":"Mon, 23 Sep 2024 15:53:48 +0530","guid":"https:\/\/tanayg.com\/blog\/an-extraordinary-code-editor-libreoffice-calc\/","description":"A thought experiment in computer language design"},{"title":"Collisions in computer languages","link":"https:\/\/tanayg.com\/blog\/collisions-in-computer-languages\/","pubDate":"Sat, 17 Aug 2024 12:51:01 +0530","guid":"https:\/\/tanayg.com\/blog\/collisions-in-computer-languages\/","description":"When user input goes to the wrong place"},{"title":"This isn't a good definition of collisions and I apologize","link":"https:\/\/tanayg.com\/aside\/this-isnt-a-good-definition-of-collisions-and-i-apologize\/","pubDate":"Sat, 17 Aug 2024 10:53:48 +0530","guid":"https:\/\/tanayg.com\/aside\/this-isnt-a-good-definition-of-collisions-and-i-apologize\/","description":"

For one, I haven’t properly defined “language parser”, “language grammar” or “user input”.<\/p>\n

These terms are difficult to define, and I’m worried that any definition I assign\nto these is going to be invalidated immediately by counterexamples. I don’t want to\nget caught up in semantics right now, and I’m choosing to give up perfect descriptions in\nfavor of an ostensive definition<\/a>.<\/p>\n

With examples, I hope I am able to communicate the underlying idea, however abstract it may seem.<\/p>"}]}}