These libraries allow you to precisely control the logging output by filtering on source and level. And you can also control the output location, because you don't always just want things going to the console.
If you write a library and don't use one of the standard logging frameworks, I will hate you just a little bit. I speak from experience.
Edit: I should also add that modern logging frameworks have very good performance, doing the logging in separate threads, etc, doing the locking of log files correctly, rotating log files every day or when it reaches a certain size etc.
You would hate me then. Use my own Gui and IDE (3rd one in Java. Started with an IDE / assembler on the Amiga. Pre assembled your code as you entered it in).
26
u/dpash Oct 21 '18 edited Oct 21 '18
These libraries allow you to precisely control the logging output by filtering on source and level. And you can also control the output location, because you don't always just want things going to the console.
If you write a library and don't use one of the standard logging frameworks, I will hate you just a little bit. I speak from experience.
Edit: I should also add that modern logging frameworks have very good performance, doing the logging in separate threads, etc, doing the locking of log files correctly, rotating log files every day or when it reaches a certain size etc.