[Interest] L Word

[eric.fedosejevs at gmail.com]

So basically open source/standard Qt was considered appropriate for safety critical devices prior to the introduction of Safe Renderer in 2017, but now only commercial Qt with Safe Renderer is appropriate for that purpose.

 

Before anyone says otherwise, Qt was widely used in safety critical applications before Safe Renderer existed. See for example the text from introductory blog post about Safe Renderer:

“Industries such as automotive, medical and industrial automation, where Qt is the leading UI framework, can now satisfy safety critical requirements with Qt easier than before.”

 

From: Benjamin TERRIER <b.terrier at gmail.com> 
Sent: Monday, May 3, 2021 11:46 AM
To: Matthew Woehlke <mwoehlke.floss at gmail.com>
Cc: eric.fedosejevs at gmail.com; Qt Interest <interest at qt-project.org>
Subject: Re: [Interest] L Word

 

 

Le lun. 3 mai 2021 à 17:33, Matthew Woehlke <mwoehlke.floss at gmail.com <mailto:mwoehlke.floss at gmail.com> > a écrit :

On 03/05/2021 11.23, eric.fedosejevs at gmail.com <mailto:eric.fedosejevs at gmail.com>  wrote:
> I find this whole argument that Qt is not appropriate for functional 
> safety very puzzling. Aren’t vehicle dashboards QtC’s main market
> these days? What are vehicle dashboards if not safety critical?

Are they? I thought it was infotainment systems. There's quite the 
difference between those two. (At least in most cars; Teslas I think may 
be starting to blur that distinction, and to an extent that likely 
alarms some people.)

 

Qt is also used for vehicle dashboards.

But yet Qt is not to be used for functional safety.

That's the sole reason for the existence of Qt Safe Render, which is suited for functional safety.

 

The idea is that Qt is used to display 3D eye candy, while Qt Safe Render displays critical information.

Meaning that if Qt fails/crashes it has 0 consequences to functional safety because the Qt Safe Renderer is still displaying what's important for the functional safety.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20210503/0ad7c53d/attachment.html>