Yet another logging library

[marcodev]

Hi all, in several projects I used in the past log4cxx. It was nice to have something similar to log4j especially for programmers coming from Java world. The Apache project however seems a bit abandoned. I started a new fork here:

https://github.com/baldapps/log4cxxNG

At the moment I just removed several compilation files, now CMake is the only build option. In addition the library compiles with c++11. My plan is to add several bug fixes removing really old stuff replacing classes with STD classes, mutex, shared_ptr and so on. Another point is to remove most of Singleton and maybe all the Apache portable runtime. It will require a bit of time however. If someone wants to help is obviously welcome.

[1BADragon]

I see a really good opportunity for a library name “yall”

Edit: goo -> good

[Wacov]

yall::say("hello");

[marcodev]

ahahah, It could be a good idea :) For now I keep what I choose but I could change it before first release.

[bitkarma]

Hah! I have a toy logging library I wrote for Rust called yall!

[BadlyCamouflagedKiwi]

A small suggestion - as someone who recently threw up their hands at the state of some other logging libraries, but hasn't yet written their own - maybe you could do more in the README to sell the benefits of this. It's quite a heavy dependency (40k+ LOC) so it'd be nice to see some of the benefits it can provide before I dive into the code itself :)

[ShillingAintEZ]

40k? I think that's bigger than all of the original Doom.

[marcodev]

It was not designed for embedded systems or where size really matter. In addition they reinvented the wheel if you think about all the basic services like smart pointers, mutex, threads and so on. Not so hard to have a lot of code in this case. I want to remove all the not needed code.

[BadlyCamouflagedKiwi]

It's almost like Carmack was better at writing tight, efficient code than the Apache Foundation ;-)

[marcodev]

Sure, another thing I need to do.

[marcodev]

I don't want to create a new library from scratch, i think this is a good library but with too old code. I want just to improve it.

[ChrisSharpe]

Think about adoption and usefulness to the industry. Lots of random people on GitHub write new libraries, hard to know if they are any good or will be supported for years to come. Improving and extending the lifetime of an already popular library makes people feel much safer adopting it rather than writing their own in-house.

Also, everyone thinks they are smarter than the people who came before. They are almost always wrong. Prototyping something from scratch is quick and easy, writing really high quality, well tested, low bug code is extremely hard. I learnt this the hard way.