By “Syslog-ng Engineer” do they mean a C systems programmer who can fix bugs and add features to syslog? that’s a rather different role from being an admin; even if, depending on the size of the operation, it make sense to give both roles to the same person
Besides Journal not being available on non-Linux, there are a could of reasons for using syslog: it can log to a remote server for instance. Journal does have a remote logging capability, but at best you have to run two log sinks in parallel, at worse it’s a non starter because everything that’s not a Linux box (network routers, VMware hosts, IDS appliances) can’t speak to it
Another is fine filing and retention. With syslog you can say things like “log NOTICE and above from daemon XYZ to XYZ.log and keep 30 days worth; log everything including DEBUG to XYZ-debug.log, keep no more than 10MB”. With Journal you rotate the entire log or nothing, at least last I looked I couldnt find anything finer. There are namespaces, but that doesn’t compowe, the application needs to know which log goes into which namespace
And Fabrice Bellard, the original author of ffmpeg, went on to create qemu which pretty much made open-source virtualization possible. Also TCC (even if I don’t think that one is widely used), he established a world record for computing decimals of Pi using a single machine that had ~2000× less FLOPS than the previous record, and so much more…
Just under half of the Internet: https://www.google.com/intl/en/ipv6/statistics.html
Inside the
lambdaexpression you can have a comprehension to unpack thekeyslist to get the same sort of uplet as your “manual” example, like this:>>> items = [{"core_name": "a", "label": "b"},{"core_name": "c", "label": "d"}, ] >>> keys = ["core_name", "label"] >>> tuple(items[0][k] for k in keys) ('a', 'b') >>> sorted(items, key=lambda d: tuple(d[k] for k in keys)) [{'core_name': 'a', 'label': 'b'}, {'core_name': 'c', 'label': 'd'}]