[Development] Deprecating modules with 5.5

Björn Breitmeyer bjoern.breitmeyer at kdab.com
Mon Feb 9 09:26:53 CET 2015

Well start with the easiest understanable reasons. People come from old 
platforms whith old applications and they don't know what their upcoming 
hardware platforms will be, so they decide why not go to Qt first and then 
decide, which platform is usable for us. Thats a pretty common theme and if 
you stop supporting the old platforms you likely won't get those customers.
Besides its something were you can earn money.

Putting pressure on a vendor is in most cases not achieving much. Even really 
really big companies are screwed if some important vendor in their stack isn't 
getting their job done, its one of the reasons why the chosen hardware is most 
likely not bleeding edge, as there are timeframes to meet until product 

Then there are industries which need certified operating systems for their 
field, they don't have the option to use the newest yocto and if they decided 
to use one kind of os the certification process most likely binds them to this 
os for the complete product lifetime.

So yes they are putting the burden on us, because they can't reliably put them 
somewhere else. You might ask why should we take the burden, because those 
companies are paying quite a bit of money too get what they need if it 
actually helps.

And yes of course we would like to use newer compiler versions, but in most 
cases with the option c++11 support how much extra pain do we have? Embedded 
is just not like desktop that even goes for gcc on linux.

Björn Breitmeyer | bjoern.breitmeyer at kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Germany: +49-30-521325470, Sweden (HQ): +46-563-540090
KDAB - Qt Experts - Platform-independent software solutions 
Am Sonntag, 8. Februar 2015, 10:25:51 schrieb Thiago Macieira:
> On Sunday 08 February 2015 19:15:18 Giuseppe D'Angelo wrote:
> > Il 08/02/2015 17:58, Thiago Macieira ha scritto:
> > > So we come back to this question again and again: if you can't upgrade
> > > the
> > > OS and upgrade the compiler, why do you want to upgrade Qt?
> > 
> > Because people want to use the latest features / bugfixes for developing
> > their product, and yet they need to target such platforms...
> Indeed, but that is putting the burden on us. They should instead insist
> with their vendors to get a newer platform and put the burden on them. Or
> next time, make sure you use a device that can run Linux so you can easily
> rebuild with Yocto -- every 6 months you get a new toolchain and sysroot
> with the latest updates. I'm going to say that if you chose a vendor that
> won't upgrade, it's your fault and you should live with the consequences.
> Anyway, every time this comes up, the answer is the same: we will drop those
> platforms once they become too much of a burden to support and prevent us
> from doing new things. That's why OS X 10.6 went away.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5920 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150209/255e6a1a/attachment.bin>

More information about the Development mailing list