He follows through with an entire rant about people using "2022-10-26 14:59:42" to represent dates instead of 1666789167 Unix timestamps, and JSON in general. I

He follows through with an entire rant about people using "2022-10-26 14:59:42" to represent dates instead of 1666789167 Unix timestamps, and JSON in general. If that's really your best example then meh... I use JSON and string time formats because it's just easier to inspect things with curl or whatnot and gives a nice balance between human-readable and machine-readable, which I rather like for APIs. I do the same with database stuff, so "select * from foo" can be easily read. It can be quite helpful in debugging and the performance difference (even with compression) is just negligible in most cases. But what do I know ... I'm just a farmer. Now excuse me while I go shove my computer down a shredder and go do something else.