Announcement

Collapse
No announcement yet.

KDE Plasma 5.5 On Wayland May Be Ready For Early Adopters

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by Jumbotron View Post

    Didn't fool me a bit. Just calling out KDE's bullshit policy of releasing BETA and even ALPHA software and not making it plain to the common user out their looking to move from the Windows or Mac world. And not holding distros to account that include their beta or alpha software without verbiage that makes it plain that this version of a distro is likely DANGEROUS and will almost certainly break your system if you install it on a production machine.

    Or better yet....just have a private alpha and beta release.

    Let Microsoft be the only ones who let their user base be the REAL beta testers. Like they did with the release of Windows Vista. That's how we got Windows 7. We got Windows 7 only after 10's of millions of Windows users unwittingly became Windows Vista beta testers for a couple of years.

    That's why I consider KDE 5 as the Windows Vista of Linux.

    then you are back to blaming the distros for having it on the install screen, not the KDE team who put out plenty of warnings to the community which, unless i'm mistaken, includes the distros. And please forgive me for not taking any notice of your opinion of KDE5 seriously as its shit

    Comment


    • #32
      Originally posted by smitty3268 View Post
      I know that one has already been fixed.


      That one's a little hard to believe - how did you find the other bugs if it always crashes right when you start it?
      Because it auto restart the libraries and then it works.

      Comment


      • #33
        well after all this non sense zerg of troll posts, there are 2 facts that could need revision:

        1.) Yes, is always the distro simply because no regular user have the expertise to build the entire KDE system(or gnome for that matter) on its own, so is OBVIOUSLY work of the distro to provide those packages and since they normally know better is LOGICAL to assume they actually read any upstream warnings. Also note is not weird for some distros to actually break userspace(like using certain ffmpeg version against upstream best warnings). Beside todays is easy to add information to sessions and packages, so a simply (Experimental) suffix in the plasma session is nothing that requires a Phd to do, so there is no justification for this too happen outside bleeding distros like Arch or Gentoo(in those is your own fault)

        2.) Evidence suggest some distro packagers are unable to read warnings, so maybe a more obvious versioning system should be help KDE avoid unstable code to land in "stable" distros(Gnome idea of pair version for releases and odd for development seems obvious enough to do the trick)

        Comment


        • #34
          Originally posted by jrch2k8 View Post
          well after all this non sense zerg of troll posts, there are 2 facts that could need revision:

          1.) Yes, is always the distro simply because no regular user have the expertise to build the entire KDE system(or gnome for that matter) on its own, so is OBVIOUSLY work of the distro to provide those packages and since they normally know better is LOGICAL to assume they actually read any upstream warnings. Also note is not weird for some distros to actually break userspace(like using certain ffmpeg version against upstream best warnings). Beside todays is easy to add information to sessions and packages, so a simply (Experimental) suffix in the plasma session is nothing that requires a Phd to do, so there is no justification for this too happen outside bleeding distros like Arch or Gentoo(in those is your own fault)

          2.) Evidence suggest some distro packagers are unable to read warnings, so maybe a more obvious versioning system should be help KDE avoid unstable code to land in "stable" distros(Gnome idea of pair version for releases and odd for development seems obvious enough to do the trick)
          About 2): The problem with even numbers for stable and odd numbers for testing is that odd number are often used to break things. Then when it eventually gets released as an even number it's still broken. That's why the linux kernel stopped doing that junk. All you end up with is a bunch of broken odd numbers followed by a bunch broken even numbers where none of them are compatible.

          Comment

          Working...
          X