console.logs in production code is not fucking acceptable.

who cares? Nobody but geeks use the console anyway

@antigermanist > "who cares?"

I don't. I have them in my production (Blazor) code right now.

@PaperTrail we have frickin' cout shit from 20 years ago in our code. I actually wanted to get rid of the spam from it and did a hack for that suppressed cout output unless you put in -d to enable it again.

@PaperTrail do they log out highly sensitive data like the ones I found on our production app?

you know what, I'm gonna do it even harder from now on.

depends? if it's Webdev, there's nothing called "sensitive data". if Console has access to it, presume that any bad actor with physical access to website-in-session does too

@int32 > "do they log out highly sensitive data"

No, a lot of "Here" and "This value should not be null, but here we are."

a dude everyone liked at the company was putting alert boxes into production code, tehe

Yeah, they should go through some kind of pipe so that they also show up in issue tracking like sentry

If it contains sensitive data, then absolutely !.

Otherwise, cool stuff can be found in such logs in older games.

So, all in all, definitely depends on the environment && data in the logs.

@int32 Under what obscene circumstance is that data accessible to the browser? If it can be printed to the console, it's accessible without it.

@cuddlyogre backend API calls spew out a bunch of unnecessary data that the front end doesn't require to operate. It's the architect's way of doing things, apparently it's better to just return as much data as possible to get started with and then clean it up later. Which never happens :D

@PaperTrail If it's a bunch of things like "here" and "this" and random text like that, then it doesn't bother me too much, but when it's massive objects with all of the backend API data in it, no.