Comment by Etheryte

1 month ago

In most languages and frameworks logging is as simple as import, initialize, done. Here it's far from it.

11 comments

Etheryte

Reply
pjmlp  1 month ago

Really, which ones?

Because anything Java, .NET and Python, it certainly requires configuration and related infrastructure.

  • Summershard  1 month ago

    > .NET

    I think you haven't used .NET in a while. Nowadays, logging is absurdly easy to configure. Heck, you usually don't even need to configure it, because the basics are already included in most templates. You just use the Logger class and it works.

    The only time you have to spend more than 30 minutes on it is when you use some external logging libraries. And most of them are quite sane and simple to use, because it's so easy to create a custom logging provider.

    • pjmlp  1 month ago

      I use it almost every day.

      Java, .NET and nodejs are all over the place around here.

      The point was without configuration.

      Logger class doesn't do the work for production monitoring, without additional configuration so that its output appears on the necessary production dashboards.

  • Etheryte  1 month ago

    Log4j can be as simple as add the dependency and you're good to go. Of course, you can do fancier setups and bridge your logs wherever where it is more work, but out of the box, it's very straightforward and batteries included. I have a very hard time believing you're seriously arguing the case that some of the most commonly used languages don't have good options for logging.