Parsing JSON is indeed a minefield. However, a commenter in HN has a suggestion: Use postscript instead of JSON. It has a binary format, has comments, and generally looks much better. Here is their provided example:

  <<
    /first_name (John)
    /last_name (Smith)
    /is_alive true
    /age 27
    /phone_numbers [
      <<
        /type (home)
        /number (212 555-1234)
      >>
      <<
        /type (office)
        /number (646 555-4567)
      >>
    ]
    /spouse null
  >>

And I agree, it is much better than JSON. There are many other interesting things to like here. For one, the keys are symbolic. There is only one character `/` indicating the keys in a dictionary (indicated by `<<`). This reduces the visual clutter to a great extent. Using `<<` for dictionaries is also great.  Dictionaries are one of the largest units in such formats containing data, and it is better to use two characters for their delimiters. By using `()` for strings, it provides a starting and ending delimiter for strings, and is better visually parsable than `"`. There are no commas in arrays. or dictionaries, removing the question of trailing commas. Overall, PON (Postscript Object Notation) is much better designed than JSON for human readability.

Is fussing the Australian spelling for fuzzing?

One great thing about LLMs such as GPT is that I no longer have to suffer through the very condescend "Oh you are asking for X, but surely you meant Y?" followed by closing the question as duplicate/irrelevant etc.

Thank you Naveen and Deb from Macquarie cloud services for the wonderful talk at SOFT3202 today!

Thank you Naveen and Deb for the wonderful talk at SOFT3202 today!

Pet peeve; I have a fair number of applications open in multiple machines. When something beeps due to some activity, I have no way of knowing which application it was. I wish that the operating system (MacOS in this case) gave me some way to identify which application beeped.

Seems training your users to work around your buggy software is a thing. I have lost count of the number of times I have had to work around buggy Microsoft office :(. The latest one is the disappearing email. Write a detailed email, and *poof* it is gone.