[Interest] MSVC not-the-latest: are you using it? why?

Elvis Stansvik elvstone at gmail.com
Sun Jan 22 23:08:00 CET 2023

> MSVC not-the-latest: are you using it? why?

Yes, using VS 2019.

I can only speak for us, but we simply haven't had any really
compelling reason to upgrade our compiler.

Turning the question around: If you have no need for the
features/improvements that a newer compiler would bring, why would you
upgrade it? It's a non-zero amount of work to switch.

In many places, if you can't make a (somewhat) direct connection to
something revenue-generating, such as a client case, it's not going to
get done unless there's unexpected extra time available.

That said, we would have no problem with Qt dropping support for VS
2019. We are using a somewhat old 5.12 version of Qt anyway, mostly
for same reason as we are not using latest compiler.

So perhaps better wait for someone that is staying on top of the
latest Qt to give their view. I can imagine that there that do that to
get improvements/bug fixes, but which rarely update their compiler.
It's quite rare to be affected by a compiler bug after all.


Den sön 22 jan. 2023 kl 17:19 skrev Thiago Macieira <thiago.macieira at intel.com>:
> In this case, MSVC 2019, which is still supported.
> I'm trying to understand why people don't upgrade their Visual Studios. In the
> past, they used to use different and binary-incompatible VC runtimes, so large
> projects often needed to stick to a single version because of different teams
> needing to otherwise have a flag day.
> But that hasn't been the case since MSVC 2015. So, are you still sticking to
> older MSVC releases years after there's a new one? Why?
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Cloud Software Architect - Intel DCAI Cloud Engineering
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> https://lists.qt-project.org/listinfo/interest

More information about the Interest mailing list