Back to the channels

#java

09:48 enoq trying to step through spring security and its abysmal docs again, looks like the blogosphere has been completely taken over by AI crap
09:49 enoq I'm trying to figure out if adding your custom AuthenticationProvider with @Component injects it into all security filter chains which I don't want
09:49 enoq at least looking at ProviderManager it seems like it should inject a list of providers from the global scope
10:50 hassoon meh
11:06 enoq that coupled with the decline of SO is kinda bad
11:06 hassoon SO ?
11:11 nimaje stackoverflow.com
11:11 hassoon ah
11:11 hassoon al lthe blame on the damn AI
11:11 hassoon all the *
11:12 hassoon SO is still useful though, to some extent
11:12 hassoon i think a google search now is more useful than a SO, because it generates an AI response for you from SO and other sources combined
11:26 deebo brewing a cup of tea and reading the tea leaves is more useful than google
11:28 jreicher I've actually found gemini summaries quite useful because they provide sources. Most of the time I click on those.
11:29 deebo they're usually ok, just have to verify everything
11:29 hassoon deebo: good.. idea
11:29 hassoon i only use deepseek when i try to toy with AI
11:30 hassoon or try to brainstorm something
11:30 jreicher deebo: but that's acceptable, no? I wouldn't expect AI to be much better than a junior RA.
11:32 deebo well it's the best available since google itself is complete ass now
11:32 deebo tried using duck duck go for some time, but they were really bad with local language synonyms etc, so it was impossible to find what i wanted
11:33 deebo google is good at that, but then pushes ad based results or seo bullshit
11:47 jreicher deebo: while I'm not interested in defending google, if you describe it as "ass" that implies something better? What would that be?
11:52 deebo i don't think there really is, which is the sad part
11:58 jreicher My hope is that AI will kill SEO.
12:01 dreamreal It's just going to change it
12:02 jreicher I agree, but I don't think there's any "just" aboutit.
12:09 dreamreal well, there never was, SEO was always a moving target
12:11 jreicher I've always thought it was a fool's errand.
12:12 dreamreal I've never been able to do it well, myself.
12:12 jreicher And the nice thing about that - if I'm right - is that it becomes really easy to identify the fools.
12:12 dreamreal I read stuff that I wrote that's had SEO applied and it's... just.. kinda gross
12:12 dreamreal As an author you have to decide what's more important: rent or your precious words
12:15 jreicher dreamreal: just make up some shit about Miley Cyrus.
12:16 deebo need coding articles written like recipe articles
12:16 dreamreal Will pass on that, know very little about her
12:16 deebo i still remember the darkening days and my grand mothers stories about virtual threads around the fireplace
12:16 dreamreal I've been actually happy with the stuff I've been writing lately, although I don't know that there's a lot of new ground I can cover on the topics
12:17 deebo every morning i take my coffee in my office at my desk and open hackernews and realize it's just AI news now
12:17 LaSombra Such is life nowadays
12:18 dreamreal News FROM AI or ABOUT AI?
12:18 deebo probably both
12:19 dreamreal There's certainly some aspect of that, but HN tends to downvote anything AI-related reflexively
12:19 deebo it's like articles about the latest shovels and peoples comparing shovels to previous models, but then never digging any holes
12:19 dreamreal I posted a human-written article and the AI summary of the article to show teh difference and teh summary got flagged as AI
12:19 dreamreal just imagine: an AI summary, prefixed with "this is the AI summary of the article," got flagged as AI!
12:23 LaSombra Can never be too sure :)
12:23 jreicher deebo: I have a paid subscription to a paper newspaper that is delivered to my house daily, and I pick up the free local newspaper weekly (again, paper).
12:23 dreamreal well, whn it's attributed directly to an AI it's probably a safe bet
13:55 ne555 good morning, `list.stream().map(x -> x.get()).filter(x -> Objects.nonNull(x)).forEach(x -> { ... })`, say that `list` holds `WeakReference`, ¿is that map-filter correct or may bite me later?
14:04 dreamreal does it work
14:07 nimaje what problems are you expecting there?
14:20 fizzie On a completely unrelated note, isn't the whole point of Objects.nonNull that you can use it to write just `.filter(Objects::nonNull)` instead of a lambda?
16:00 cheeser fizzie: the whole point? probably not, but you can do that, yes.
16:14 fizzie Can't really think why you'd write `Objects.nonNull(x)` over `x != null` if not using it for a method reference. Well, I guess you could be allergic to punctuation.
16:14 fizzie (The JavaDoc does mention that "This method exists to be used as a Predicate, filter(Objects::nonNull)".)
16:16 dreamreal $work uses it as a simple validation all the time since it's a method call instead of a statement.
16:16 dreamreal So if you can't think of why, well, I get it, but that's a limited imagination.
16:17 dgregory I think it's fine - the `.get()` converts the `WeakReference` to a strong reference or null, and `nonNull` ensures that the `forEach` only runs if the `WeakReference` wasn't already cleared
16:20 Para It produces an NPE with better trace as it nowadays includes the symbol name. Or so I've told.
16:20 Para I have never bothered to actually check :P
16:20 fizzie It doesn't throw an NPE.
16:20 Para Well AssertionError or whatever :D I'm just doing the motions.
16:21 fizzie It doesn't throw anything.
16:21 fizzie Objects.requireNonNull would, and I have no beef with that.
16:21 cheeser requireNotNull() throws.
16:21 Para well that.
16:22 fizzie `Objects.nonNull(x)` just returns the boolean value of `x != null`.
16:24 fizzie I'm a little curious about what sort of context requires (or at least prefers) a method call rather than a different kind of expression.
16:25 Para I guess it prevents people from flipping the args and having stupid errors that way but ehhhh.
16:26 waz important issue of the day!
16:27 cheeser i can see people putting in to a list of validations. that's honestly not far off from how a predicate would be used in many ways but not entirely.
16:32 fizzie I admit I've written `x != null` where I actually (atypically) meant `x == null`, I guess it might have been harder to accidentally mix up `Objects.nonNull(x)` and `Objects.isNull(x)`.
19:37 jbosmans i still always write .filter(o -> o != null)
19:38 jbosmans and very often same for other method refs
19:38 jbosmans subjective an opinion as ever
19:53 dreamreal not sure it matters if it works
20:40 dmlloyd if you use Objects::isNull instead of o -> o != null, it theoretically could create fewer lambda instances