1. 4

  2. 6

    This is not very coherent. It’s talking about a stale bot (OK, I don’t like them either) that only posts after years have passed? An inaccurate summary of KOffice/Calligra? Something about GNU Cobol?

    1. 3

      Agreed on the coherency, if you review from the bottom up it makes slightly more sense. From what I can tell KDE used to do this manually, it eventually fell off as a manual task for whatever reason. A year goes by, someone turns on the automation for it.

      I’m not sure how abandonware is KDE’s fault however. Or what context in which is KDE abandonware relevant.

      1. 1

        I interpreted it as a re-take on jwz’s CADT rant. Software gets written; bugs are reported; developers have lost interest in working on the bugs; eventually the whole area is deprecated and removed; somebody else writes a functionally similar thing; that also has bugs; etc.

      2. 4

        As someone who recently made an effort to use KDE, I think this is trying to talk about the larger phenomenon where large chunks of functionality in the KDE ecosystem either don’t work, or it’s unclear how they’re supposed to work.

        In particular, I really wanted to use the contact and calendar features in KDE, but at the end of the day I was unable to. I never even figured out whether it was a NixOS packaging issue or an upstream thing. So when I read this article, it’s telling me that there’s a lack of headcount to work on known bugs - which makes sense, it’s mostly volunteers and KDE is no longer exciting to users. So that’s what I take from it, and what I suspect the author would have said directly if they knew how.