On 2017-04-14, Fri 13:29:54 CEST stakanov wrote:
In data venerdì 14 aprile 2017 12:06:49, Rüdiger Meier ha scritto:
Both possibilities would be
better than what we have now.
Why?
IMO because it’d be better for the KDE project to focus on the core experience while some applications could be split off to provide benefits to all environments, not just KDE. NIH syndrome is bad. There’s no good reason to keep gnome-keyring and kwallet around when independent password managers like KeePassXC could be integrated instead (just think of people who are using more than one machine/OS). There’s no reason for both gvfs and kio to exist when the same could be achieved with better FUSE integration. There’s no reason to have a completely useless KDE-specific web browser (as much as I used to like it in the old days). There’s no reason to have a KDE-specific BitTorrent client that is unable to seed properly and tends to crash. There’s no reason for a KDE-specific terminal emulator (qterminal exists now). There’s no need for most of kded. There’s no need for a KDE-specific screenshot utility. There’s no need for Calligra.
In short, putting tons of completely superfluous and half-baked code out of commission and eventually replacing it by integrating existing solutions which are actively maintained by larger communities might be the way to go. By this: there is no need for KDE. There is QT instead? What a desktop proposes is the choice of the project. The problem is: a) why KDE does reinvent the wheel to provide a totally new super experience with an application that, compared to the one before is less performing, with less features and full of bugs.... happened more then once. b) some parts of the use of a desktop are totally neglected (unfortunately I am no programmer but: e.g. there is google born tesseract...but no one ever did write an interface for it. Same is true for a good and feature complete scanprogramme. c) it is true that the survival of a KDE application is not clear. Even successful once are suddenly out of focus, abandoned but without asking for anybody to take over. Just when it is too late it is always: nobody wanted to take over. But maybe communication channels are not working when I see the reactions when these things come to terms. This is BTW not the NIH syndrome but "let us reinvent our own wheel to feed our ego". d) if you have native qt applications what have you won? Nobody impedes you to
In data venerdì 14 aprile 2017 14:15:24, Martin Herkt ha scritto: port them to qt if they are KDE. Nobody forbids the authors to programme in QT. Still, if KDE tomorrow wants, the may use anther thing than QT. Imagine that QT changes violently their license or has a problem of financing. Then having programmed for QT would have been a bigger problem. When KDE was available for windows I know nobody(!) that ever used it or wanted to use it. What makes you think that people would like to go to QT. They could haven done long time ago with razor QT. But the fact is: they didn't. As far as I know people complain rightfully because of the continuous change of desktop. KDE claims that the impelling reason for change is always new technology of QT. For me the dependence on QT will break the neck of KDE sooner or later. When Plasma 5 will be ready there will be a new incompatible QT. This is what I (sus) expect. I once met people on FOSDEM claiming to be the responsible programmers of Kmail. They did not seem to be too serious about the problems they had caused in the past and laughed it off. For me, currently, KDE is not reliable enough in the most important core application for business use and this is also breaking slowly its neck. PS. SDDM is an example were the whole thing leads. It is NOT a KDE application. It is full of bugs and (that's the most funny part) people THINK it is a KDE application and blame KDE for it. QT webkit had and AFAIK has a big problem. The blame however was for KDE. Intel and Nvidia do not give a FF (and it is not firefox) about improving their buggy graphics driver. AMD seems to simply drop old cards without supporting them any more. But the symptoms of Plasma crashing because of a faulty graphics is often told to be KDEs fault. This is also a clear communication problem. YMMV -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org