Timeline for Using source code instead of XML/JSON or other custom serialization schemes and binary file formats
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2022 at 15:57 | comment | added | jaskij | @BerinLoritsch and yet, as I mentioned in a comment on the question, GitLab does this. Theirs is probably a slightly different use case, security wise, as having access to a configuration file on someone's git server means hope is already lost. | |
| May 19, 2022 at 20:29 | comment | added | Berin Loritsch | I've added additional information. In my job I have to where many hats, and both my engineering and security senses are tingling with the hidden dangers in the approach you are pursuing. | |
| May 19, 2022 at 20:28 | history | edited | Berin Loritsch | CC BY-SA 4.0 | Updated to address the real issue. |
| May 19, 2022 at 20:05 | comment | added | Berin Loritsch | How does that change just because configuration is source? I would argue the problem becomes harder with code as config because you don't have the option of translating an older config format to a newer one. | |
| May 19, 2022 at 6:49 | comment | added | Reto Höhener | Thank you for your input. Sorry, my question is not about version control, but how to handle renaming or structural changes in the data, and still be able to load old files. | |
| May 18, 2022 at 18:39 | history | edited | Berin Loritsch | CC BY-SA 4.0 | added 550 characters in body |
| May 18, 2022 at 17:38 | history | answered | Berin Loritsch | CC BY-SA 4.0 |