Login
You're viewing the functional.cafe public feed.
  • Oct 15, 2026, 2:20 PM

    @neal I think there's a big difference between "I've scratched my itch, and now I'm considering putting in effort that would compensate others who deal with my itch", and "I've scratched my itch, and now I want someone else to maintain it for the rest of eternity". the former, I'm interested in; the latter, I don't really care about

    💬 1🔄 0⭐ 0

Replies

  • Oct 15, 2026, 2:32 PM

    @whitequark @neal It was "'my' itch was for a trivial use case to work with macos, which involved a one line change to fix a spec compliance bug". The response was silence for 4 months, followed by false accusations when I promoted a bug attachment proposed patch to a PR, and demands for elaborate synthetic testing on Windows for hypothetical out of scope situations, all with an attitude.

    💬 1🔄 0⭐ 1
  • Oct 15, 2026, 2:33 PM

    @lina @neal I wouldn't describe a spec compliance bugfix as "scratching an itch" regardless of context, at least personally. certainly it is not something that increases maintenance burden (my issue with some 'drive-by contributions')

    💬 1🔄 0⭐ 0
  • Oct 15, 2026, 4:08 PM

    @whitequark @lina I legitimately do not care if you're a drive-by contributor or not. I would endeavor that if you come to one of my projects and do a drive-by contribution, that you might find it useful to stick around and do more, but deprioritizing drive-by contributors messes up the whole pipeline longer term.

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 15, 2026, 5:59 PM

    @neal @lina it's the same logic as that beind rejecting LLM-generated patches. it takes far less effort to propose a kludge than it takes to review, test, and later maintain it. not recognizing this is completely unsustainable

    💬 0🔄 0⭐ 0