Re: KDE4/Qt4 removal from openSUSE Factory

On 2019-03-29 9:45 a.m., Wolfgang Bauer wrote:
> Am Freitag, 29. März 2019, 10:50:42 schrieb Carlos E. R.:
>> [useless rant] IMHO, something is wrong in library design if going from
>> one version to the next is that difficult.

Hmmm.


> As Luca wrote already, it's actually often relatively easy to port 
> applications from Qt4 to Qt5 or kdelibs4 to KDE Frameworks5 (unless they still 
> use Qt3 compatibility stuff that got removed in Qt5).

Hmmm.  OK, then.

> 
> But Amarok is a huge project, and too few people are actively working on it 
> (as usual...).

Maybe that tells us something.
Why are so few people working on it?
Is it not just that it is huge but that it is complicated and obscure and not
easy to comprehend and become familiar enough to work on?  I haven't looked at
the source of Amarok but I have for a few other projects and it made me wonder
about the mind of the creator.  I was always taught to design and program with
maintainability in mind.

> The main technical difficulties (AFAIK) were porting the context view (which 
> used Plasma, and got rewritten from scratch using QtQuick/QML directly), and 
> the scripting engine (which used QtScript that is still available but 
> deprecated in Qt5).

As in "Depreciated" meaning "Its going away in the next revision", perhaps


> Anyway, as always, ranting/complaining/critizing doesn't help much.
> More people would need to step up and actually do some work... (I'm not 
> addressing you or anybody in particular here, it's just a general statement)

It could also mean that the roots of the application and its design assumptions
go too far back and it is unmaintainable and should be left to die.

Or perhaps a completely new *design* created that just happens to have the same
name ...  I've seen that happen in the more commercial word for a variety of
products.

-- 
"We stand behind all of our products, except for the manure spreader."
 -- Corporate motto of an equipment manufacturer
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]