4 ms·

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, th

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.

marcosdumay 5y ago
> 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.
- ashtonkem 5y ago
  > 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.

marcosdumay 5y ago

> 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.

ashtonkem 5y ago
> 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.