3 ms·
Yes and it's been considered by many a Java developer before: https://stackoverflow.com/questions/11359187/why-not-use-java-util-logging https://stackoverflow.c
by brabel 3y ago
Yes and it's been considered by many a Java developer before: https://stackoverflow.com/questions/11359187/why-not-use-java-util-logging https://stackoverflow.com/questions/11359187/why-not-use-jav...
It's an old and tired API, inefficient, slow... you can do better by using the newer System.Logger which fixes those issues, mostly: https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/lang/System.Logger.html https://docs.oracle.com/en/java/javase/17/docs/api/java.base...
- zappb 3y agoThe system logger is intentionally designed for use by standard Java classes, not by user code. It’s to help unify the various ways JDK functionality configures logging so that it can be delegated to a proper library like Log4j.
- raverbashing 3y ago> It's an old and tired API, inefficient, slow.. And of course the python logging library was inspired on it. Sigh... One part of the std python lib that needed a big overhaul
- imtringued 3y agoThis is so typical of Java. People still write tutorials about the obsolete HttpUrlConnection in 2023, when HttpClient exists. In fact, almost every API in the Java standard library is bad and once they realize the necessity to replace it, they add a second actually usable API that nobody uses.
- brabel 3y agoThis seems typical of every language that survives for more than 20 years.
- MrBuddyCasino 3y agoDidn’t know about System.logger(), interesting! Everyone seems to use slf4j via Logback.