BTW in the unix-like world, the UNIX philosophy gives a pretty definite rationale behind the design decision made in this context.
Please, take the time and read this
All your base are belong us!
You're doing it wrong.
People talk about text files like they're magical and more robust. The fact is that in order to access a text file you need about 14 pieces of software, and for one of them you have a lot of options as to which piece of software you use. If it is in a binary format you need about 14 pieces of software, and you have less choice about that one piece.
Are you trying to disprove your own point now?
Your reply addresses zero of my arguments. Try again.
I've yet to see a standard text file editor which is able to view a text file in
What kind of retarded straw-man or obvious troll is that? Where do you think databases store their data? In the magic data cloud? Besides, what does the 'non-standard' part even *mean*?
Besides, when your hard drive crashes it is pretty hard to read the text files on it. On the other hand, when the configuration is stored in a replicated database, your cluster can keep on chugging along.
If the hard drive crashes, data may be lost. If the data is stored redundantly, data may be safe. News at 11.
Seriously, where to you *think* databases store their data?
On a side point,
Even most admins who love text files in
Really, it's beyond embarrassment. Git by its very nature *deals with* text files.
But yes, I am a systemd proponent.
Of course you are.
You'll be happy that it [tl;dr]
I really don't care. I abandoned Linux in favour of the BSDs when it started to smell, and you're the perfect example of why it does that nowadays
Wow, I just puked a bit.
Bus error -- please leave by the rear door.