Interesting #blog #article on multi- #gigabyte #json files: https://thenybble.de/posts/json-analysis.. It looks like I really need to learn more about #gnu #parallel , seems like a pretty cool tool!
Good lord #yaml is crap compared to #json https://ruudvanasseldonk.com/2023/01/11/.. It's simply too #complex and suffers many of the problems that #xml does as it tried to #replace it...
The #cli #tool #jc is pretty cool, being able to #parse common #commandline #terminal #tools into #json so that they are more #machine usable: https://kellyjonbrazil.github.io/jc/ This is excellent.
Interesting #idea for #atching #json #file http://jsonpatch.com/ I wrote something like this quite a while ago, but not nearly this good! #merging #json is actually really quite tough!
Very cool #interactive #tool for #interactive #json #viewing and #editing https://pauljuliusmartinez.github.io/
Really nice #discussion about providing #json #output for #cli #utilities https://blog.kellybrazil.com/2021/12/03/.. The previous method was some kind of #random #formatting that was always hard to #parse and had little #consistency !
#json is somewhat a #mess - but it's good enough that if you use it in a reasonable way, it will be fine: http://seriot.ch/projects/parsing_json.h.. Just don't #abuse the #edgecases ... Otherwise you will be stuck with a #library #specific #implementation and won't have #portability ...
Interesting, now I am wondering whether #deadsocial should have a #relational #database such as #sql or a non-relational database such as #nosql https://lowendbox.com/blog/sql-vs-nosql-.. Given that currently everything is in #json #format - the transition to #nosql would likely be far easier! #deadsocial was specifically #designed with this #datastructure in mind!
The #unix #philosophy us a pretty powerful one - #doonethingwell https://blog.kellybrazil.com/2019/11/26/.. #jc is a nice little program for #parsing #json data on the #commandline - I have personally used it and was quite impressed. Highly recommended.
@barray on Sun Aug 15 03:08:15 UTC 2021 said: &eI would go further with my support of #json - I have been able to give a #configuration file to people who have never touched it before in their lives, and they figured out how to edit it within a few seconds. #yaml on the other hand has tonnes of tiny edge cases that cause it to fail to parse.I've personally experienced #yaml (through #pandoc #configuration ) and #json through many other programs, and I *much* prefer JSON. As mentioned in the following article, YAML is *actively* hostile towards any kind of complex structure: https://utcc.utoronto.ca/~cks/space/blog.. The other benefit for something like JSON is that it is parsed by #js really easily and looks like a #cfamily language.
I've personally experienced #yaml (through #pandoc #configuration ) and #json through many other programs, and I *much* prefer JSON. As mentioned in the following article, YAML is *actively* hostile towards any kind of complex structure: https://utcc.utoronto.ca/~cks/space/blog.. The other benefit for something like JSON is that it is parsed by #js really easily and looks like a #cfamily language.