News for hackers. Stuff that matters.
Re:Third High Severity CVE in Log4j Is Published by marcosdumay on Sunday December 19, 2021 @10:04AM (#29614454)
Why is there any problem in restarting your logging system? There is nothing in a logging system that could be harmed by a restart. Restarting it is exactly how you should handle changes, because it deals with plenty of stuff that isn't reconfigurable on a lower level.

The only way to make a "reconfigurable" logging system is by having a stable facade that restarts everything behind it. But that extra layer does not belong on a logging system, there are plenty of other things you need to make "reconfigurable", and now you are adding an extra layer into each of them, instead of having only one on your main entry point.

Pushing that feature down into the logging system is the choice that maximizes complexity and minimizes functionality.

Re:Third High Severity CVE in Log4j Is Published by lazide on Sunday December 19, 2021 @04:05PM (#29618409)
If you turn on debug logging to see why somewhere weird is happening, and the only way to do that is to completely restart the entire system - good luck figuring out why a large class of weird things happen!
Re:Third High Severity CVE in Log4j Is Published by ashtonkem on Sunday December 19, 2021 @10:11AM (#29614518)
You act as if “restarting” the logging system is easy and doesn’t require the same facade that you decry for a reconfigurable one. With dependency injection, there are loggers everywhere in the system, possibly in sections of the code you didn’t even rewrite. Restarting such a system while continuing to run everything else is just as complex as reconfiguring, possibly more complex.

Also, I noticed you didn’t answer my question about whether you’re a Java developer.

Re:Third High Severity CVE in Log4j Is Published by marcosdumay on Sunday December 19, 2021 @11:13AM (#29615026)
> about whether you’re a Java developer

I was once, but haven't used it professionally for a while. It's on my "I'd rather not" list, but not strongly so.

Oh, and now that you described it with so many details, the attachment to complexity does look more like addiction than love.

Re:Third High Severity CVE in Log4j Is Published by ashtonkem on Sunday December 19, 2021 @10:04PM (#29621150)
> I was once, but haven't used it professionally for a while.

This is why I ask. Java has changed a lot since ~1.8, and it is super common to see ex or non java developers making grandiose and sweeping statements about a community and language that they are no longer part of. Having developed in Java on and off since ~1.7 and Spring 3, I can certainly say that I have seen a strong movement towards less complexity and more convention. It's not perfect by any stretch, but I think saying that the space is "in love with complexity" is incorrect.

You of course don't have to go and re-use Java on my suggestion. We all have our preferences, and that's ok! But I would generally recommend against such sweeping and dismissive general statements about a culture that you are no longer part of. Things change, and your experience back then is probably not representative of things today.

> Oh, and now that you described it with so many details, the attachment to complexity does look more like addiction than love.

There's a fine line between disagreement and insult, and you are over it.