3 ms·

You mean JSON, right? (I'm not joking, the JSON looks much more readable and cleaner to me than the S-Expressions)

• zeveb 7y ago
  The S-expressions look much cleaner to me: parentheses and characters, with a few quotes where needed. Meanwhile, the JSON is a mess of curly brackets, square brackets, commas, quotes &c. All the field names are strings, not symbols or tokens. To my eyes, JSON is an embarrassingly ugly format, while S-expressions are clean & readable.
  • CDSlice 7y ago
    Funny, to me the commas, culry brackets, and square brackets actually make it more readable. They provide context like "this is a list of stuff" or "this is a key:value mapping" which make it much faster to mentally parse it. The S-Expressions on the either hand are a sea of parentheses with no way to quickly tell what's a list or mapping or whatever without closely looking at each item. Having to quote the symbols is terrible though.
    • zeveb 7y ago
      > The S-Expressions on the either hand are a sea of parentheses with no way to quickly tell what's a list or mapping or whatever without closely looking at each item. I guess that's part of the point from my point of view: it's not about hash tables or objects or even lists, but about what they represent. In my view focusing on the implementation (a hash table mapping strings to hash tables mapping strings to numbers or strings) is looking at the trees and missing the forest.