Aswin Kumar

Rest in peace, Pappa ❤️ I promise I will become a man that you are proud of

We are revising our developer API policies: We will no longer allow apps that reward users for posting on X (aka “infofi”). This has led to a tremendous amount of AI slop & reply spam on the platform. We have revoked API access from these apps, so your X experience should start improving soon (once the bots realize they’re not getting paid anymore). If your developer account was terminated, please reach out and we will assist in transitioning your business to Threads and Bluesky.

Is there anything we can do to keep you around? Can you check my DM. Thanks!

TOON is doomed to fail. TOON struggles with nested data. Independent tests already show accuracy dropping compared to JSON. The moment your structure gets complex, TOON becomes a liability. On top of that, JSON is the default structured language. That’s the native dialect. JSON appears constantly across the internet >APIs return JSON. >Dev tools save logs in JSON. >Configs, datasets, telemetry, and modern documentation rely on JSON. >GitHub is full of JSON snippets and structured examples. So models see JSON thousands, even millions, of times during pretraining. So, you don’t get bonus points for switching to TOON. In some cases, you get worse results. Even if TOON worked perfectly, model providers could kill its moat overnight by compressing JSON themselves, adding new wire formats, or absorbing TOON-style ideas into their protocol layer. Then there’s human reality. JSON survived because anyone can skim it at 3 a.m. TOON needs new tools, new habits, and attention nobody has time for. At the end of the day, TOON is more of a middleware trick. The real winners will be systems that handle human chaos and optimize behind the scenes, without asking anyone to change how they speak.