[Development] Qt Multimedia as Add-on in Qt 6

[Florian Bruhin]

On Fri, May 22, 2020 at 02:54:24PM -0400, Matthew Woehlke wrote:
> On 22/05/2020 13.43, Jason H wrote:
> > How about I just pay - which my company already does? The lagging mobile
> > support has us considering moving away from Qt. I think this decision
> > would confirm our direction and only hasten our departure
> > from the Qt ecosystem.
> > 
> > I guess to some degree it depends on how you define "essential".
> > Clearly multimedia *is* essential
> What's "clear" to you may not be "clear" to everyone. I, personally, don't
> believe I have ever used QtMM. I can think of applications I might *like* to
> write that might use it, but plenty of applications I *do* write have no
> need for it. Most KDE applications don't need it. QtC and Designer don't
> need it.
> 
> In fact, out of the software I use in a typical day, the only stuff that
> comes to mind that might need it are:
> 
> - Gwenview (but it's more a nice-to-have)
> - Plasma? (Whatever is responsible for system notifications, anyway)
> - My web browser (except I use Firefox, which does not use Qt...)
> - Dragon
> 
> Really, the only three things I would argue *need* it are my web browser,
> media player, and the desktop environment itself.
> 
> For quite a few application developers, it is *not* essential at all.

FWIW I write a browser[1] using Qt - in its default configuration, it uses
QtWebEngine, which does not use QtMultimedia either (and uses Chromium's
multimedia stack instead).

Florian

[1] https://www.qutebrowser.org/

-- 
me at the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org 
       https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
       GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
             I love long mails! | https://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200522/77f72c53/attachment.sig>