lwlog VS analysis-pipelines

I would be very glad and honored if you drop a critique, an opinion, an idea, or want to contribute to the project:https://github.com/ChristianPanov/lwlog

I am working on a c++ logging library, which you can check out here: https://github.com/ChristianPanov/lwlog

I would be very glad and honored if you drop a critique, an opinion, an idea, or want to contribute to the project:https://github.com/ChristianPanov/lwlog

• UTF support

I have done benchmarks against spdlog, and you can take a look at them in the README in the repository

Also benchmarking is not done correctly in the main repository. I have benchmarks in my private dev repository and I am benchmarking either with picobench or nanobench. So if you want to benchmark, do NOT rely on the Benchmark.h file in the project (it's a temporary file that is meant to be removed)

I would be very glad and honored if you drop a critique, an opinion, an idea, or want to contribute to the project: https://github.com/ChristianPanov/lwlog

Do you know some of your users? They might be the ones to ask for help on your project description. Also, for feedback, as a user of open-source projects I don't usually volunteer detailed feedback. If I have a problem or need a new feature I might fill in an issue, but sometimes if there are no guidelines on how to report/request things I feel like my feedback wouldn't be welcome. So maybe add guidelines for that in the FAQ section? Doesn't have to be complex, just an invitation for people to communicate with you through issues, saying you welcome support requests and/or feature requests if you do. Issue templates might be useful too. (An example of mine for inspiration) And if you have specific points you want users to give feedback on, don't hesitate to add a message redirecting to a dedicated issue in your Readme.

I'd like to submit the CRANE toolbox, dedicated to helping humanities researchers studying online racism with their data analysis tasks. The project managed to carry on after its initial creation during a hackathon. Right now we are maintaining it but can't develop any further because the skillsets needed are more specific and advanced.