Slackware Developer Not Happy With KDE5 Development

[caligula]

I think the funniest thing is that KDE developers think they're using agile methodology. It's the worst f**ing clusterf*ck I've seen. How can you f*ck it so bad after 3 complete rewrites. KDE3 is totally different from KDE2 and for KDE4 they rewrote massive parts of the system. Now for KDE5 it's the same. You totally rewrite. And you have all the knowledge of agile methodology, TDD, regression testing. Still they barely manage to ship anything that compiles. At the same time they're using more modern versions of C++ which should really help with reliability. How can it be?

It's really surprising how broken things are. Kde 3.5.10 was pretty good. It mostly worked. It took several years till 4.2 or 4.3 to actually get anything on par with 3.5.10 in terms of reliability in the daily use of KDE as a desktop. When I use KDE4 now, the firsts things I do are disabling all bells and whistles, disabling all extra plugins and that damn nepomuk.

[jrch2k8]

I think the funniest thing is that KDE developers think they're using agile methodology. It's the worst f**ing clusterf*ck I've seen. How can you f*ck it so bad after 3 complete rewrites. KDE3 is totally different from KDE2 and for KDE4 they rewrote massive parts of the system. Now for KDE5 it's the same. You totally rewrite. And you have all the knowledge of agile methodology, TDD, regression testing. Still they barely manage to ship anything that compiles. At the same time they're using more modern versions of C++ which should really help with reliability. How can it be?

It's really surprising how broken things are. Kde 3.5.10 was pretty good. It mostly worked. It took several years till 4.2 or 4.3 to actually get anything on par with 3.5.10 in terms of reliability in the daily use of KDE as a desktop. When I use KDE4 now, the firsts things I do are disabling all bells and whistles, disabling all extra plugins and that damn nepomuk.

KDE2 = Qt2.x -- basically lacked a lot of functionality and hardware acceleration
KDE3 = Qt3.x -- initial feature boost and some hardware acceleration changed the API quite extensively
KDE4 = Qt4.x -- almost complete feature set and almost good enough hardware acceleration but lacks wayland and opengl/es support
KDE5 = Qt5.x -- basically every feature you could want is there, full C++11 support, superb hardware acceleration(XCB, opengl/es, egl, wayland, threadweaver) and KDElibs got integrated extensively back to Qt

about your question, well because is on development and require bleeding edge code and the same happen with gnome, the problem is erick is not trying to build gnome 3.15.X snapshot in slackware otherwise he will rant about it too for the same reason(even on arch take lot of patience to build gnome snapshots).

Btw KDE5 is not a rewrite but a refactoring, aka they took all the code in kdelibs that was redundant with Qt and moved it back to Qt(for example all the awesome in KApplication class got back to QApplication class) and after all the clean up was done the modularised the remaining KDElibs code in small specialised libraries(platform independant mostly) (for example Ark now links with Qt5 and Karchive/KIOlibs only).

After that migrate a Qt4 application to KF5 is basically replace old KDElibs classes for the Qt5 ones and refactor your makefiles linking process.

[pingufunkybeat]

Btw KDE5 is not a rewrite but a refactoring

This.

[Awesomeness]

Their workflows appear to be such that they write code which depends on other modules? code which only exists in a Git repository.

Could it be that he expects all applications as well? He using the name ?KDE5? indicates that. The applications have not yet been released and obviously only live in git?