• 0 Posts
  • 2 Comments
Joined 2 months ago
cake
Cake day: August 17th, 2026

help-circle

  • no JSON

    I find this really frustrating.

    There’s always going to be new escape sequences on the horizon. Each one having their own custom serialization format is just going to slow down adoption and be a source of bugs. Using an established serialization format that just works and is readily available is not an unreasonable ask. It doesn’t have to be JSON. But, at this point, it has basically won. Every single example program mentioned in the spec is already dealing with JSON. Every shell environment that has base64 most likely has jq. What is supposedly being saved by not using it and instead making tool authors do something custom? It just adds more stops in integration hell.


    score 1 · canonical