That newfangled Journal thing

The performance+security advantages of structured binary data are undeniable.
Yes, you can get performance by re-reading syslogs and generating indexes...

People get scared because they use cat/grep, but most setups include the *ugly* logrotate, so you *zcat anyway.
In the end, for people who like text, a "journalc log --pretty=xxx" will probably be available...

What bothers me is:
- If journald wants to become a defacto standard, then the file format should be discussed, others may have some insight on this. Other logging/tracing/generic file formats exist, and people would appreciate if they could be referenced so that we know they have been reviewed (and the wheel is not reinvented) when designing a new file format.
Where's the mailing list, and the wiki for the design info ?
Right now it seems pretty obscure.
The file format should consider other software implementations
Nobody wants it to change in 1 year, but it should be future-proof.
- Despite what the release document says, journald could be separated from systemd, as a separate library
- Finally, and this has nothing to do with journald, software that don't provide syslog logging and write their own logs without any good reason !