I vaguely remember hearing this this was only really available for toy code and that this function created the class ignored the arguments and qualified println when you compiled it, so it wasn't actually that useful?

[–] bigboismith@lemmy.world 3 points 2 days ago (1 children)

Printing to console is often only used for toy code anyway.

[–] silasmariner@programming.dev 5 points 2 days ago (2 children)

Wait, how do you debug your code?

[–] firelizzard@programming.dev 1 points 5 hours ago

… with a debugger

[–] Traister101@lemmy.today 3 points 2 days ago (2 children)

A logger? Console prints are shitty in general but especially when you have an actual logger already

[–] SlurpingPus@lemmy.world 7 points 2 days ago (1 children)

You know what println never did? Run arbitrary code on my toaster.

[–] Traister101@lemmy.today 1 points 2 days ago

Neither did Log4j in basically all cases, some maniac just put arbitrary code callbacks into their logger, undocumented and enabled by default. The insane part isn't the feature itself it's the fact it's enabled by default in a logger of all things.

[–] silasmariner@programming.dev 2 points 2 days ago (1 children)

Oh man, I thought that was one of the classic jokes :'( I am out of touch

[–] Traister101@lemmy.today 1 points 2 days ago (1 children)

People in my experience are actually very serious about the standard out to debug log which is... baffling. Same people generally outright refuse to learn how to use a debugger in languages where those are pleasant

[–] silasmariner@programming.dev 1 points 2 days ago* (last edited 2 days ago)

Oh I'm completely serious. The joke is that everyone does it but everyone knows not to do it. I started doing it when I first ran into problems debugging actor contexts, and never stopped.

The good printlns become logs, obviously