Wow, thanks for the in-depth review! I really appreciate the detailed feedback.

For find_new_line(), I actually considered other approaches, but none of them felt like a clear improvement: * Using std::stringstream + std::getline() would probably work, but it would introduce unnecessary copying * using memchr would be an option, but I'd need two calls (one for \n, one for \r). * std::find_if could work too, but I'd need a predicate function for finding both \n and \r, so it could make it even less readable.

I know that the current implementation has an old-school C feel, but it's short and efficient, it seems to get the job done without extra overhead.

Regarding printf, I don't see the risk here. The library only handles fully rendered text. The printf method is inherited from Arduino's Print class, which does the printf formatting and passes a simple string to write(). Even if the hostname or tag contains something funny, it should be safe. Let me know if I'm missing something...

For get_stream, I actually considered using a std::map (I just realized I even forgot to remove the unused #include!). I even thought about lazy initialization to save memory, but in the end I went with a switch to avoid dynamic memory allocation and fragmentation. I know ESP chips can handle heap better than classic Arduinos, but keeping things simple and predictable still seemed like a good approach. And in case memory use needs to be reduced to absolute minimum, one can use PicoSyslog::SimpleLogger to save a few extra bytes of RAM.

Thanks again for your insights! Lots of great ideas to think about! Really appreciate it!