5 ms·

very cool and the person has the skills to do that. sad to see how the fully AI generated "why this matters" section in the blog gives a lingering vibe of slop.

by fock 6mo ago

sidkshatriya 6mo ago
> sad to see how the fully AI generated "why this matters" section in the blog gives a lingering vibe of slop. I am quoting this verbatim from offending section: Why this matters The traditional eBPF workflow is: write C for the BPF side, compile with clang, then write Go or Rust or Python for the userspace side. Two languages, separate build steps, multiple processes. With Whistler 1.0, the workflow is: write Lisp. The compiler, loader, and userspace application share a process. You can develop at the REPL — modify a probe, re-eval the form, see results immediately. The feedback loop is instant. Seems like a reasonable paragraph. I sincerely feel we must stop tainting things with the "slop" pejorative unless it really seems egregious. Also in 2026 is it easy to be so confident about what was generated by a human, edited by a human or generated by an LLM ? My main metric is: does the paragraph add value ? It does to me as a summary.
- rjsw 6mo ago
  The author has been using AI for other Lisp projects.
  - tmtvl 6mo ago
    Yes, but it seems to me like atgreen takes care to ensure the result is decent, so I would hesitate before calling it slop. I may be wrong, though.
  - varjag 6mo ago
    He's been also doing Lisp projects before GenAI, so…
- kuschkufan 6mo ago
  That dude just wanted everyone to know that he found the emdash, that he is so vigorously looking for in everything he reads these days.
  - Fellshard 6mo ago
    It's more the repeated 'rule of three' that's getting me here. That said, this is a relatively tame tack-on to a very meaty post, not worth harping on unless the project itself has similar issues.

5 ms·

very cool and the person has the skills to do that. sad to see how the fully AI generated "why this matters" section in the blog gives a lingering vibe of slop.

by fock 6mo ago

very cool and the person has the skills to do that. sad to see how the fully AI generated "why this matters" section in the blog gives a lingering vibe of slop.

sidkshatriya 6mo ago
> sad to see how the fully AI generated "why this matters" section in the blog gives a lingering vibe of slop. I am quoting this verbatim from offending section: Why this matters The traditional eBPF workflow is: write C for the BPF side, compile with clang, then write Go or Rust or Python for the userspace side. Two languages, separate build steps, multiple processes. With Whistler 1.0, the workflow is: write Lisp. The compiler, loader, and userspace application share a process. You can develop at the REPL — modify a probe, re-eval the form, see results immediately. The feedback loop is instant. Seems like a reasonable paragraph. I sincerely feel we must stop tainting things with the "slop" pejorative unless it really seems egregious. Also in 2026 is it easy to be so confident about what was generated by a human, edited by a human or generated by an LLM ? My main metric is: does the paragraph add value ? It does to me as a summary.
- rjsw 6mo ago
  The author has been using AI for other Lisp projects.
  - tmtvl 6mo ago
    Yes, but it seems to me like atgreen takes care to ensure the result is decent, so I would hesitate before calling it slop. I may be wrong, though.
  - varjag 6mo ago
    He's been also doing Lisp projects before GenAI, so…
- kuschkufan 6mo ago
  That dude just wanted everyone to know that he found the emdash, that he is so vigorously looking for in everything he reads these days.
  - Fellshard 6mo ago
    It's more the repeated 'rule of three' that's getting me here. That said, this is a relatively tame tack-on to a very meaty post, not worth harping on unless the project itself has similar issues.