• Bro666@lemmy.kde.socialM
    281·
    1 year ago

    I think that KDE’s track record shows that devs do not remove stuff just because. Quite the contrary.

    But sometimes stuff does get removed and often it is because or it is unmaintained (and been so for a while), or because it is built on some old technology that cannot be replicated in the new environment without a complete rewrite.

    In both cases, the reason a feature is discontinued boils down to a lack of resources.

    Fortunately, the solution is simple: do your part.

    KDE is a porous, grassroots and welcoming community. Join us and become part of the effort to build one of the largest and most diverse collections of end user, publicly-owned, free software projects in existence.

    I know, I know: “but I can’t code”, etc., etc. But there are many things you can do to help. You can help organise Akademy 2024, you can translate menus and system messages, you can write documentation, draw wallpapers, design icons, edit videos, support booth staff at events, triage and report bugs, or just donate and contribute to financially supporting devs who still have to hold down pesky day jobs that get in the way of coding for KDE… The list goes on and on.

    The point is, regardless of your level of technical knowledge, the more resources you free up elsewhere, the more time the people who do know how to code will have to maintain and translate software and features in the new Plasma 6 environment.

    • PseudoSpock@lemmy.dbzer0.com
      1·
      1 year ago

      What was the purpose of this message? Was it to prevent conversations about concerns and worries in this thread? Because it seems unnecessarily defensive. Is there something we should be worried about?

    • skookumasfrig@sopuli.xyz
      51·
      1 year ago

      That’s how I felt with KDE 1 and 2. I left it alone for a while and recently came back to KDE 5 after getting a steam deck and now I’ve switched my desktop to it.

  • David Sugar@floss.social
    5·
    1 year ago

    @kde @kde@lemmy.kde.social In a sense it feels long overdue, but it also does take time and feels very new…

    My question is what happens to Qt5? I feel like it’s because of #KDE it continues to be maintained at all, and yet many other projects still utterly depend on Qt5, even believe they don’t need to migrate to Qt6 or otherwise refuse to. I believe HelloSystems is in this category.

    • milliams@lemmy.world
      4·
      1 year ago

      I wouldn’t expect so. Firstly, the deadline for packages getting into a distro is usually several months before the release date, and secondly that they’ll likely (understandably) cautious about an x.0 release for production.

    • Sina@beehaw.org
      1·
      1 year ago

      I used to think it might 2026 (the first year after Windows 10’s demise), but seeing how increasingly shit Windows 10 is update after update, (weren’t they only supposed to be security patches now?) they might just force an unprecedented number of ppl to switch.

  • PseudoSpock@lemmy.dbzer0.com
    64·
    1 year ago

    Watch this end up like the KDE 4 fiasco. “We removed everything you loved, ain’t it great!” Please don’t let me down again, KDE.

      • PseudoSpock@lemmy.dbzer0.com
        11·
        1 year ago

        Watch this end up like the KDE 4 fiasco. “We removed everything you loved, ain’t it great!” Please don’t let me down again, KDE.

        How was that rude, I didn’t insult anyone. I even said please when asking not to let me down again. If you want to deny KDE 4 was bad, go ahead, but that is an honest criticism (and one shared by many, as I’m sure you are aware), but to call honest feedback rude is disingenuous. I don’t appreciate you changing the context to try to vilify me. Lastly, the CoC is never mentioned on the KDE Community Wiki until “22:08, 12 December 2019‎ Vinzv talk contribs‎ 6,507 bytes +3,285‎ Migrated content from https://manifesto.kde.org over here”, which is long after KDE 4, which is already listed on that same page as “Historical Information” as far back as 2011. So from what I can tell, KDE 4 was probably never covered under the CoC, don’t think it existed yet. So it wouldn’t be protected from honest feedback, if that is what the CoC is being used here to prevent.

        • noncommutativegeometry@mastodon.social
          1·
          1 year ago

          @PseudoSpock @Bro666 I am just reading this as an outsider, but I can say that if the first message was something like “I hope this time features are going to be preserved. I still remember the transition from KDE 3, where I lost x, y and z” it would have sounded different than “watch this end up like the KDE 4 fiasco”. In this second sentence I assume that your expectations are already set, for a bad release.

          Now I’m genuinely curious: is something important to you being removed from Plasma 6?

      • PseudoSpock@lemmy.dbzer0.com
        22·
        1 year ago

        If you were a fan of KDE 3 and got hit with KDE 4, you would remember how awful that was. [CoC doesn’t prevent that truthful statement] Simply removing features due to a lack of resources is [censored for your unfavorable CoC]. Don’t release until it is equal to or better than your previous release [Constructive advice]. So what if it takes 10 years. Releasing less ready software, as in missing features, is how you got KDE 4 and Wayland. [Another truthful statement.]

        And one more edit: Using a code of conduct to deny the problems with previous releases and honest criticism is, shall we say, [censored again due to your unfavorable CoC]. It’s already been announced features are being cut. So how am I wrong here?

  • H2207@lemmy.world
    1·
    1 year ago

    I’ve recently switched from Gnome to KDE in preperation for Plasma 6. I’m definitely noticing some rough edges even on 5.27, so I’m highly looking forward to 6.00

  • David Sugar@floss.social
    1·
    1 year ago

    @kde @kde@lemmy.kde.social what I do like from what I have seen of this is the idea, which I love in Xfce, of trying to produce the best possible version of KDE at the time, rather than wasting real user’s time by completely re-imagining and re-inventing what a desktop even means to stroke private egos. That is the difference between greater value construction over time, and it’s continual destruction.