Allowing only valid JavaScript identifiers to be unescaped keys is also a bit quirky (You have to quote reserved keywords).

But they will never change any of that because it would break JavaScript compatibility.

Overfitting is the problem of having too little training data for your network size.

And it doesn't play like normal solitaire. You can move any card, no matter what's on top of it. That makes it much easier.

- instead of trailing commas, how about making them completely optional? It's not like they are needed in the first place.

- curly braces for top-level objects could be optional too.

- For a data exchange format, there should really be a standard size for numbers, like i32 for integers and f64 for floats.

- parsing an object with duplicate keys is still undefined behavior.

I don't want to programm anything without comments.

I guess you can easily convert from use yaml or json5, but all the examples are still in json.

I found this: https://github.com/nanochess/RayTracer

  $..book[?@.price<10].title

  find_key = (data, key) => {
    if(data instanceof Array){
     return data.map(x=>find_key(x, key)).flat()
    }
    if(data instanceof Object){
     let res = Object.keys(data).map(x=>find_key(data[x], key))
     if(data.hasOwnProperty(key)){
      res.push(data[key])
     }
     return res.flat()
    }
     return []
   }

  find_key(data, "book").filter(x=>x.price < 10).map(x=>x.title)

  $.store.book[?@.price < 10].title

  [x['title'] for x in data['store']['book'] if x['price'] < 10]

  data.store.book.filter(x=>x.price < 10).map(x=>x.title)