Chat Logs

  1. enoqtrying to step through spring security and its abysmal docs again, looks like the blogosphere has been completely taken over by AI crap
  2. enoqI'm trying to figure out if adding your custom AuthenticationProvider with @Component injects it into all security filter chains which I don't want
  3. enoqat least looking at ProviderManager it seems like it should inject a list of providers from the global scope
  4. hassoonmeh
  5. enoqthat coupled with the decline of SO is kinda bad
  6. hassoonSO ?
  7. nimajestackoverflow.com
  8. hassoonah
  9. hassoonal lthe blame on the damn AI
  10. hassoonall the *
  11. hassoonSO is still useful though, to some extent
  12. hassooni 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
  13. deebobrewing a cup of tea and reading the tea leaves is more useful than google
  14. jreicherI've actually found gemini summaries quite useful because they provide sources. Most of the time I click on those.
  15. deebothey're usually ok, just have to verify everything
  16. hassoondeebo: good.. idea
  17. hassooni only use deepseek when i try to toy with AI
  18. hassoonor try to brainstorm something
  19. jreicherdeebo: but that's acceptable, no? I wouldn't expect AI to be much better than a junior RA.
  20. deebowell it's the best available since google itself is complete ass now
  21. deebotried 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
  22. deebogoogle is good at that, but then pushes ad based results or seo bullshit
  23. jreicherdeebo: while I'm not interested in defending google, if you describe it as "ass" that implies something better? What would that be?
  24. deeboi don't think there really is, which is the sad part
  25. jreicherMy hope is that AI will kill SEO.
  26. dreamrealIt's just going to change it
  27. jreicherI agree, but I don't think there's any "just" aboutit.
  28. dreamrealwell, there never was, SEO was always a moving target
  29. jreicherI've always thought it was a fool's errand.
  30. dreamrealI've never been able to do it well, myself.
  31. jreicherAnd the nice thing about that - if I'm right - is that it becomes really easy to identify the fools.
  32. dreamrealI read stuff that I wrote that's had SEO applied and it's... just.. kinda gross
  33. dreamrealAs an author you have to decide what's more important: rent or your precious words
  34. jreicherdreamreal: just make up some shit about Miley Cyrus.
  35. deeboneed coding articles written like recipe articles
  36. dreamrealWill pass on that, know very little about her
  37. deeboi still remember the darkening days and my grand mothers stories about virtual threads around the fireplace
  38. dreamrealI'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
  39. deeboevery morning i take my coffee in my office at my desk and open hackernews and realize it's just AI news now
  40. LaSombraSuch is life nowadays
  41. dreamrealNews FROM AI or ABOUT AI?
  42. deeboprobably both
  43. dreamrealThere's certainly some aspect of that, but HN tends to downvote anything AI-related reflexively
  44. deeboit's like articles about the latest shovels and peoples comparing shovels to previous models, but then never digging any holes
  45. dreamrealI posted a human-written article and the AI summary of the article to show teh difference and teh summary got flagged as AI
  46. dreamrealjust imagine: an AI summary, prefixed with "this is the AI summary of the article," got flagged as AI!
  47. LaSombraCan never be too sure :)
  48. jreicherdeebo: 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).
  49. dreamrealwell, whn it's attributed directly to an AI it's probably a safe bet
  50. ne555good 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?
  51. dreamrealdoes it work
  52. nimajewhat problems are you expecting there?
  53. fizzieOn 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?
  54. cheeserfizzie: the whole point? probably not, but you can do that, yes.
  55. fizzieCan'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.
  56. fizzie(The JavaDoc does mention that "This method exists to be used as a Predicate, filter(Objects::nonNull)".)
  57. dreamreal$work uses it as a simple validation all the time since it's a method call instead of a statement.
  58. dreamrealSo if you can't think of why, well, I get it, but that's a limited imagination.
  59. dgregoryI 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
  60. ParaIt produces an NPE with better trace as it nowadays includes the symbol name. Or so I've told.
  61. ParaI have never bothered to actually check :P
  62. fizzieIt doesn't throw an NPE.
  63. ParaWell AssertionError or whatever :D I'm just doing the motions.
  64. fizzieIt doesn't throw anything.
  65. fizzieObjects.requireNonNull would, and I have no beef with that.
  66. cheeserrequireNotNull() throws.
  67. Parawell that.
  68. fizzie`Objects.nonNull(x)` just returns the boolean value of `x != null`.
  69. fizzieI'm a little curious about what sort of context requires (or at least prefers) a method call rather than a different kind of expression.
  70. ParaI guess it prevents people from flipping the args and having stupid errors that way but ehhhh.
  71. wazimportant issue of the day!
  72. cheeseri 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.
  73. fizzieI 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)`.
  74. jbosmansi still always write .filter(o -> o != null)
  75. jbosmansand very often same for other method refs
  76. jbosmanssubjective an opinion as ever
  77. dreamrealnot sure it matters if it works
  78. dmlloydif you use Objects::isNull instead of o -> o != null, it theoretically could create fewer lambda instances