3 comments

  • pixelesque1 hour ago
    &gt; We deal mostly with source code, so the text we fold is overwhelmingly ASCII and making it run at memory speed is the single most important thing we can do. Everything else just has to keep the rare non-ASCII path from spoiling it.<p>Semi-on-topic: I&#x27;ve noticed that many LLMs via coding agents (ChatGPT and Claude at work with my CoPilot account, and DeepSeek 4 and ChatGPT in pi.dev at home) really seem to like using unicode &#x2F; emoji characters for things like arrows (for things like test value ranges), crosses and ticks (for pass vs fail in test comments), instead of plain ASCII. Codebases are almost exclusively ASCII chars to my knowledge, although they&#x27;re UTF-8 files.<p>I&#x27;m not yet using agents to write code (only do code reviews, write example prototypes I then copy bits of, and helping craft tests), but I&#x27;m likely to get there soon, and I&#x27;m sure it&#x27;s possible to prompt them NOT to do this, but has anyone else noticed this? I wonder if that changes things over time for them if this is a common theme of increased non-ASCII output?
    • codebje33 minutes ago
      Codebases written by native English speakers are almost exclusively ASCII, but codebases written by speakers of languages other than English frequently have non-ASCII content, even if only in the comments, but languages which support it often wind up with non-ASCII identifiers, too.<p>I do not believe that emoji like crosses and ticks are particularly common at all, for any language, but LLMs seem to have picked up heavy use of them from somewhere and inserted them into code (and everything else) they generate.<p>LLM training sets will very likely include the massive corpos of non-English open source code from sites like Gitee, but would be unlikely to generate responses heavily influenced by them unless you&#x27;ve done specific things to make that happen - prompt in Chinese, try to make use of a library only available with Chinese source and&#x2F;or documentation, perhaps. I&#x27;ve not seen it happen, but I am a light user of LLMs.
    • chuckadams56 minutes ago
      Using emoji for status indicators on the console is a trend that pre-dates LLMs. First mainstream app I can recall doing it was Yarn.
  • claudetard2 hours ago
    This is good technical content, but it&#x27;s obvious that an AI wrote it.
    • Groxx1 minute ago
      [delayed]
    • agency1 hour ago
      Agreed. This is genuinely interesting content, but there is no doubt in my mind that &quot;The two operations diverge on real characters—ß, İ, final sigma—which is why lowercasing as a stand-in silently produces wrong matches.&quot; is LLM output.<p>Are we doomed to spend the rest of our professional and personal lives reading AI output?
      • inigyou1 hour ago
        Yes.<p>&gt; This is genuinely interesting<p>Are you sure you&#x27;re not an LLM yourself?
        • agency1 hour ago
          I thought I wasn&#x27;t, but you&#x27;re making me second-guess myself.
  • inigyou1 hour ago
    TLDR: they implemented case folding with a lot more SIMD via autovectorization.<p>&gt; almost every fold preserves the UTF-8 length or shrinks it, but two outliers grow—U+023A (Ⱥ) and U+023E (Ɀ) are 2 bytes each yet fold to 3-byte characters (ⱥ, ɀ)<p>Fix this by reversing it. Fold ⱥ to Ⱥ instead of the other way around. The search index won&#x27;t only consist of lowercase characters any more, but that never mattered.
    • persedes45 minutes ago
      This is a nice follow up to the other SIMD article that was posted here a week or so ago hah.
    • PaulDavisThe1st1 hour ago
      [dead]