| |||||||||||||
The cake, it was a lieThe cake, it was a liePosted Sep 26, 2012 4:49 UTC (Wed) by khim (subscriber, #9252)In reply to: The cake, it was a lie by jospoortvliet Parent article: GStreamer 1.0 released
Well, if all the technologies behind you are changing each every 7 years, yes, you're changing all the time. Only if you use CADT model. The fact of the matter: MacOS, Windows, other platforms regularly redo all the levels of stack - yet somehow people can use all these creations without additional layers of indirections. Why? Oh, it's easy: yes, they change "state of the art" once per about five-to-seven years, but they continue to keep supporting older methods, too. Exactly like GStreamer is doing. I can see the pluses of an indirection layer for something which changes regularly and forces you to port everything right away, but for something like GStreamer where upstream is sane and seriously thinks about maintainability... this is just an additional complication.
(Log in to post comments)
The cake, it was a lie Posted Sep 26, 2012 12:22 UTC (Wed) by sebas (subscriber, #51660) [Link]
Upstream simply does not satisfy KDE's requirements for binary and source compatibility, namely BC and SC across a major release lifecycle.
GStreamer's BC and SC have been broken more than once since KDE 4.0, which means we (and every developer using the KDE platform) would be stuck with old and unsupported versions.
That's the exact opposite of maintainability.
|
|||||||||||||