Announcement

Collapse
No announcement yet.

KDE 4.9.3 November Update Fixes 86 Bugs

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

  • #16
    Originally posted by energyman View Post
    compared to the huge articles whenever some gnomer farts in the wrong direction this 'article' is just pathetic. Thanks Michael for once again reminding me why I do not pay but instead look at shiny ads.
    It's a minor bug fix release. What should he write a longer article about?

    Comment


    • #17
      Originally posted by Akka View Post
      It's a minor bug fix release. What should he write a longer article about?
      compare the kde 4.9.3 article with the gnome 3.5.3 article. Just for fun.

      Comment


      • #18
        Originally posted by pingufunkybeat View Post
        Well, quite a few things turned out to be good enough: Digikam, K3b, Amarok. All of these benefitted from having KDE libraries at their disposal, and were (arguably still are) best-in-class applications.
        Digikam has been glitchy up until the past year, and k3b has been around so long it's actually the oldest program I remember, so it had time to mature. On top of that, k3b is a frontend (to the same programs that most other linux cd burning programs use), and correct me if I'm wrong but amarok is a frontend too. I see no problem whatsoever of developers making fontends that are DE specific, in fact i think it's the best idea of all - it encourages everyone to contribute to the same core functionality while allowing people to interface with it in their own way. That way everyone wins - the users get a more reliable backend, the backend devs get more support for a better product, the graphical designers don't have to start from scratch, the DE devs can easily integrate the program, and therefore eliminates the need for further backend competitors. In the Linux world, its nice to have alternatives but why re-invent the wheel when you can just use the frame of it but add your own tires and hubcaps?
        Last edited by schmidtbag; 11-07-2012, 09:11 PM.

        Comment


        • #19
          Originally posted by schmidtbag View Post
          Digikam has been glitchy up until the past year, and k3b has been around so long it's actually the oldest program I remember, so it had time to mature. On top of that, k3b is a frontend (to the same programs that most other linux cd burning programs use), and correct me if I'm wrong but amarok is a frontend too. I see no problem whatsoever of developers making fontends that are DE specific, in fact i think it's the best idea of all - it encourages everyone to contribute to the same core functionality while allowing people to interface with it in their own way. That way everyone wins - the users get a more reliable backend, the backend devs get more support for a better product, the graphical designers don't have to start from scratch, the DE devs can easily integrate the program, and therefore eliminates the need for further backend competitors. In the Linux world, its nice to have alternatives but why re-invent the wheel when you can just use the frame of it but add your own tires and hubcaps?
          A lot of the KDE applications are frontends to common stuff.

          All of the media players go through phonon, which is a frontend for gstreamer, vlc, and a xine (there may be others, but gstreamer is the recommended and possibly only maintained one now)
          The instant messenger is moving to be a telepathy frontend.
          Okular uses the poplar pdf reading library.
          konqueror/rekonq uses webkit and embeds other kparts.

          Dolphin, plasma, and the PIM and office stuff are the only ones that are really 'ground up' everything else is built on common linux tech.

          Comment


          • #20
            What should he write a longer article about?
            Originally posted by energyman View Post
            compare the kde 4.9.3 article with the gnome 3.5.3 article. Just for fun.
            Compare this one, just for fun:

            http://www.phoronix.com/scan.php?pag...tem&px=MTE5MzE

            If there's not much to write about, there's just not much to write about. And that's a major release.

            Comment


            • #21
              Originally posted by halfmanhalfamazing View Post
              Compare this one, just for fun:

              http://www.phoronix.com/scan.php?pag...tem&px=MTE5MzE

              If there's not much to write about, there's just not much to write about. And that's a major release.
              Thus implying; If Michael doesnt write about it, it doesnt exist. What sad and poor world you live in. Here is a clue for you. A poor write up at phoronix doesnt mean shit. Go read the real release announcement og test it. Unlike KDE the unity or gnomers does se new action. Gnome 3.6 actually deserves some applaud for not being deadware like the non-releases put out by KDE.

              The sad news of a early death by a KDE developer saved the last KDE release. If she didnt there was nothing to write about. Claire saved KDE for 4.9. Who will it be for 4.10?

              Comment


              • #22
                Originally posted by schmidtbag View Post
                Many of those hundreds of newly reported bugs have been fixed or are duplicates but worded differently. The problem KDE is having is distros like Debian keep using ancient releases when nearly every release of KDE is a cluster of bug fixes and nothing else. Also I've found KDE tends to break config files rather easily, which emulate a bug. you can reduce the amount of bugs if you delete your KDE settings, which is inconvenient considering e level of customization KDE has to offer. If you don't use the entire KDE suite I'm sure you can reduce bug encounters by using other programs.

                I agree that KDE has more than they can really handle. There are whole sections they could cut out that a DE doesn't need such as koffice (while it does have its perks, its better to just make libraries to libreoffice to add integration), konqueror, nepomuk, kopete, and so on. I've found many KDE programs to be very sub-par, I'd rather just use DE-neutral programs with KDE plugins for integration. as I've said before, linux is getting too much competition within itself. software isn't getting the dedicated attention it used to because everyone wants to do their own thing.
                Absolutely, if users are experiencing issues upon updates to KDE then the best fix is to delete the config files and restart which will reset KDE to defaults. Then the user can re-configure the settings they had before.

                Bugs are always evident but if some variables are eliminated then the true bugs will be easier to spot

                Comment


                • #23
                  Originally posted by funkSTAR View Post
                  Thus implying; If Michael doesnt write about it, it doesnt exist. What sad and poor world you live in. Here is a clue for you. A poor write up at phoronix doesnt mean shit. Go read the real release announcement og test it. Unlike KDE the unity or gnomers does se new action. Gnome 3.6 actually deserves some applaud for not being deadware like the non-releases put out by KDE.

                  The sad news of a early death by a KDE developer saved the last KDE release. If she didnt there was nothing to write about. Claire saved KDE for 4.9. Who will it be for 4.10?
                  The funny thing about desktops that don't suck: They don't have to go through radical changes with every major release.

                  The lack of "exciting" new things in major kde releases is due to the fact that it is a mature piece of software.

                  Comment


                  • #24
                    Originally posted by ShadowBane View Post
                    The lack of "exciting" new things in major kde releases is due to the fact that it is a mature piece of software.
                    Mature software loses its bugs, NOT its developers. So KDE is not maturing it is dying. It us quite funny to watch the vocal few in a total denial of the obvious. LuLz.

                    Gnome and unity is of course another story.
                    Last edited by funkSTAR; 11-08-2012, 03:20 PM.

                    Comment


                    • #25
                      Originally posted by funkSTAR View Post
                      Mature software loses its bugs, NOT its developers. So KDE is not maturing it is dying. It us quite funny to watch the vocal few in a total denial of the obvious. LuLz.

                      Gnome and unity is of course another story.
                      Mature projects gain and lose developers on a regular basis. I have seen nothing to indicate that there has been an exodus of KDE devs.

                      Comment


                      • #26
                        Originally posted by schmidtbag View Post
                        Digikam has been glitchy up until the past year, and k3b has been around so long it's actually the oldest program I remember, so it had time to mature. On top of that, k3b is a frontend (to the same programs that most other linux cd burning programs use), and correct me if I'm wrong but amarok is a frontend too.
                        And digiKam is a front-end to libjpeg, libpng, etc.…

                        Originally posted by energyman View Post
                        compare the kde 4.9.3 article with the gnome 3.5.3 article. Just for fun.
                        There are a few very simple reasons for that:
                        1.) SC releases don't get that many new features these days because the developers are concentrating on modernizing existing features. Frameworks 5, where most engineering effort is going in, are in development since quite some time – if the KDE devs stick to the regular 6 months cycle, KF 5.0 should be released in summer 2013. Plasma applets are being rewritten in QML – ideally looking and behaving almost exactly as the C++ versions.
                        When code is completely rewritten, it is a big change but what else would you write instead of “rewritten in QML”?
                        2.) Phoronix often features KWin separately.
                        3.) Qt is developed independently, whereas GTK is part of the GNOME project, so GTK changes should obviously be part of GNOME changelogs.

                        Comment


                        • #27
                          Originally posted by marc.collin
                          stop using ubuntu and other distribution who are not able to polish kde... and you will have not problem with kde desktop.
                          Come on, no distribution can fix the mess that KDE has become. I guess SuSE is the one with best KDE integration, and this probably cost them a LOT of time/money to be so.

                          Just have a look at bugs.kde.org and see by yourself.

                          I have stopped using KDE 2 years ago because i was fed up to fill bugs every day. None of them has been fixed, few of them have had updates from kde dev, and lot of them got confirmation from other users.

                          Comment


                          • #28
                            Originally posted by orzel View Post
                            I have stopped using KDE 2 years ago because i was fed up to fill bugs every day. None of them has been fixed, few of them have had updates from kde dev, and lot of them got confirmation from other users.
                            True. I had a quick look at the latest KDE commit digest and compared it to last year. KDE have 50 contributors during one year. So you can expect less developers giving a shit about your bugs. They will bitrot.

                            KDE lost its place to Unity. What a nice death lol.

                            Comment


                            • #29
                              Originally posted by orzel View Post
                              I have stopped using KDE 2 years ago because i was fed up to fill bugs every day. None of them has been fixed, few of them have had updates from kde dev, and lot of them got confirmation from other users.
                              You should have done it the other way around (wait 2 years then use it). KDE is way more stable than 2 years ago. It is true that there might be bugs (I can see none in the stuff I'm using), but that doesn't mean it's unusable.

                              Comment


                              • #30
                                Originally posted by droste View Post
                                You should have done it the other way around (wait 2 years then use it). KDE is way more stable than 2 years ago. It is true that there might be bugs (I can see none in the stuff I'm using), but that doesn't mean it's unusable.
                                That's the common lies coming from KDE. Even recently, i had to remove KDE from lots of user computers I administrate. I used to spend time "fixing" their KDE by removing everything related to nepomuk+strigi+plasma, which usually is enough to bring it back to a usable state, but i got fed up of this too.
                                Those were the typical kubuntu, centos, debian stuff, updated, so nothing like the even uglier early kde4.
                                It seems so common to say this, but KDE is such a bloatware nowadays. Which we used to say about windows or gnome by the time. (yes, "we", i used to be quite a big KDE fan).

                                Comment

                                Working...
                                X