The latest IntelliJ deprecates `println` :sweat_sm...

# random

[CLOVIS]

The latest IntelliJ deprecates println 😅

[CLOVIS]

KTIJ-39074 Don't deprecate println

[darkmoon_uk]

This was a mistake right? ...right???

[CLOVIS]

They want to advertise the new log point feature. They thinking warning on every println statement is a good way to do that. If you disagree, join the discussion in the issue I linked.

[CLOVIS]

Update: official recommendation is to disable the inspection if you don't like it.

[Arjan van Wieringen]

Thats a pretty wild recommendation. Like print debugging is the only usecase for println

[CLOVIS]

Exactly

[darkmoon_uk]

It's gone 😂

[Edoardo Luppi]

No no it's not gone, they've just changed the project from KT to IDEA
https://youtrack.jetbrains.com/issue/IDEA-390245

[CLOVIS]

Weird that the initial link doesn't work anymore. I'm pretty sure YouTrack used to create a redirection in that case, probably a regression in a version. From what I know of IntelliJ, it's definitely not intentional, they don't try to hide stuff like this.

[CLOVIS]

It's still not fixed in 2026.2 RC. This is your last chance to complain before it reaches stable.

youtrack.jetbrains.com/issue/IDEA-390245

[Robert Jaros]

I thought it was some kind of joke, now I see it's true 😕

[pdvrieze]

My main problem is that debugging for various non-jvm platforms is often broken. Println is then the only available option.

[CLOVIS]

Yep. From what I understand, this change comes from the IntelliJ Debugger team (not the IntelliJ Kotlin plugin team), and they don't seem to understand that Kotlin is multiplatform

[CLOVIS]

They also don't seem to understand that we don't like spurious warnings

[Dmitry Kandalov]

Regardless of multiplatform default warning for println doesn't look like the smartest decision to me. And it's shocking that it has come so far to be shipped 💩🙈

[darkmoon_uk]

Agree it's horrifying. Someone stop this madness.

[darkmoon_uk]

What next... Classes considered harmful, everything must be a captured lambda... Just arbitrary skill issue bullsh*t!

[darkmoon_uk]

This is what detekt is for

[CLOVIS]

@Dmitry Kandalov definitely comment on the issue! I don't think they realize the problem.

[phldavies]

I'd much rather a logpoint shortcut much like the existing sout (typing .log as a suffix on an expression does give you the option to add a logpoint but you have to have an expression to start with)

[CLOVIS]

Same. I didn't find how to create nicely in the UI (other than click in the margin to create a normal breakpoint, then edit it to make it non-suspending)

[oligarchokapi]

lol wtf

[CLOVIS]

Correction: you can easily create one in the UI by clicking in-between two lines.

[CLOVIS]

For anyone who's curious

The issue about the logpoint warning is the second most-voted bug fix in 2026.2, and the issue with the most comments in 2026.2. The only issue with more votes is 10 years old.

I don't understand how the warning reached stable.

[PHondogo]

It is how modern democracy work :)

[Stefan Oltmann]

Junie said no!

[tapchicoma]

IDEA-392642 Logpoints: disable inspection by default for Kotlin

[CLOVIS]

@tapchicoma that issue is not public

[tapchicoma]

interesting, I could not change visibility, but title is "Logpoints: disable inspection by default for Kotlin"