3 ms·
>and also lose the ability to roundtrip, so your app can't edit user configs I think roundtrip with comments is not feasible in general. Most code just expects
by PhilipRoman 2y ago
>and also lose the ability to roundtrip, so your app can't edit user configs
I think roundtrip with comments is not feasible in general. Most code just expects a hashmap, which it edits and then serializes back. You would need some really clever handling for comments to do it.
- eviks 2y agoWe're in luck: clever people exist and have written libraries that do the clever handling for us and support roundtripping comments!
- throwaway290 2y agoWhich works at performance cost and only until it breaks...
- eviks 2y agoLack of roundtrip means it's already broken and loses data, so upgrading to just the potential of a break is a marked improvement worth paying for
- throwaway290 2y agoCan't lose data which you don't have and in this case there are no comments in json!
- eviks 2y agoIf you close your eyes, the data doesn't disappear! Of course you have the data, it's in the comments, and the original comment explains how it got there
- throwaway290 2y agoIf someone classifies comments as data then I'd say someone needs to upgrade data architecture chops Yes the comment free spec forces to normalize what would be comments into data spec and it is frustrating to put more effort into things