[Interest] MSVC not-the-latest: are you using it? why?
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 smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] MSVC not-the-latest: are you using it? why?
Hi Thiago, On some update of MSVC-2017 to their next minor release, we got their optimization bug. It was a waste of time to understand what happened and to work-around it. jm2c Kind regards, Robert On Sun, Jan 22, 2023 at 6:19 PM Thiago Macieira wrote: > > 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@qt-project.org > https://lists.qt-project.org/listinfo/interest ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] MSVC not-the-latest: are you using it? why?
On Sun, 22 Jan 2023 at 13:18, Thiago Macieira wrote: > > 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? Medical devices/software would need to go through a whole set of revalidation if the compiler changes. On that field changes are complicated. ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] MSVC not-the-latest: are you using it? why?
> Medical devices/software would need to go through a whole set of > revalidation if the compiler changes This is understandable, but then logic would like it to be the same for the use of any new version of the Qt framework. Personnaly, I find more bugs in Qt releases than in the compiler releases. ...Qt 6.6 should not be concerned by old compilers. Philippe ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] MSVC not-the-latest: are you using it? why?
Hi, On Sun, 22 Jan 2023 at 14:28, Philippe wrote: > > > Medical devices/software would need to go through a whole set of > > revalidation if the compiler changes > > This is understandable, but then logic would like it to be the same for > the use of any new version of the Qt framework. That's a valid remark, updating Qt means there should be no issue in updating the compiler at the same time. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/ ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] MSVC not-the-latest: are you using it? why?
On Sunday, 22 January 2023 08:33:43 PST coroberti wrote: > On some update of MSVC-2017 to their next minor release, we got their > optimization bug. > It was a waste of time to understand what happened and to work-around it. That just means you had to downgrade to the previous minor version of 2017. That doesn't answer my question, though. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering smime.p7s Description: S/MIME cryptographic signature ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] MSVC not-the-latest: are you using it? why?
> 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. Elvis Den sön 22 jan. 2023 kl 17:19 skrev Thiago Macieira : > > 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@qt-project.org > https://lists.qt-project.org/listinfo/interest ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] MSVC not-the-latest: are you using it? why?
Den sön 22 jan. 2023 kl 23:08 skrev Elvis Stansvik : > > > 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 *that there are those that do that > get improvements/bug fixes, but which rarely update their compiler. > It's quite rare to be affected by a compiler bug after all. > > Elvis > > Den sön 22 jan. 2023 kl 17:19 skrev Thiago Macieira > : > > > > 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@qt-project.org > > https://lists.qt-project.org/listinfo/interest ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
