5 ms·

I migrated from Win32 to Qt two years ago. Never looked back. Much easier to program dialogs & UI. Qt gives you macOS as well. (And UWP if you insist). WinRT i

I migrated from Win32 to Qt two years ago. Never looked back. Much easier to program dialogs & UI. Qt gives you macOS as well. (And UWP if you insist). WinRT is the OS/2 of the 21st century.

Sunspark 5y ago
I have some concerns with Qt. Not the functionality, but the implementation of some of it. My primary concern is that it doesn't respect the OS's anti-aliasing settings. It defaults to making fonts anti-aliased, even if you don't want them to be. Because of this, last year I stopped updating an app using Qt. The higher resolution a display is, the less and less you need anti-aliasing so it's unnecessary in the 4K and up era. Also while I am not on a 4K display, I find AA fonts blurry compared to nice crisp hinted non-AA fonts.
- mark-r 5y ago
  As you get higher in resolution, I'd expect the difference between AA and non-AA to get less noticeable. Is that not the case?
- nyanpasu64 5y ago
  What OS and DPI are you on?
- jhgb 5y ago
  Have you tried Ultimate++, by any chance?
pjmlp 5y ago
WinRT looked great, finally .NET being like Delphi and a C++ stack that looked like C++ Builder, for those moments that .NET alone won't do it. On one side .NET Native is left to stagnate in C# 7, and C++/CX got replaced with C++/WinRT, which to this day (4 years later) still doesn't offer any kind of IDL tooling on VS (lets forget for a second that IDL exists since OLE 1.0), and requires manually merging generated files. Then to top that, we get MAUI on top of WinUI, but with the XAML format used by Xamarin. Anyone following the now 2100+ issues on Github, community calls, change of roadmap of what WinUI 3.0, Reunion and XAML Islands were supposed to be originally, and where they are going after Windows 11 announcement, can only be dismayed. They don't seem to either get the complaints, or most likely, are stuck in a position where they cannot publicly acknowledge them. OS/2 was actually much better than this with CSet++, while SOM had metaclasses and implementation inheritance, with Smalltalk and C++ support. Still, I can equally well rant about other platforms, it is all a matter of which flaws we are willing to put up with.
- n8cpdx 5y ago
  I think there's a degree of denial. I remember walking up to an engineer on the WinUI team at Build (can't remember if 2018 or 2019) and they were _shocked_ that I had complaints about UWP. They seemed to think it was a revelation. It was honestly offensive how out of touch she was. I think at least the PMs on that team do not understand the human suffering they cause by releasing such a bad product. Anyway, after a particularly awful project involving UWP and Forms UWP, I'm taking my vacation days and using them to learn Typescript, React, and Electron. Edit: if you find yourself working at Microsoft on the WinUI or UWP teams, quitting is an option. There are many good products that could use your skills and programmer labor is in high demand.
  - pjmlp 5y ago
    I guess you have put it quite well.

I migrated from Win32 to Qt two years ago. Never looked back. Much easier to program dialogs & UI. Qt gives you macOS as well. (And UWP if you insist). WinRT is the OS/2 of the 21st century.

Sunspark 5y ago

I have some concerns with Qt. Not the functionality, but the implementation of some of it. My primary concern is that it doesn't respect the OS's anti-aliasing settings. It defaults to making fonts anti-aliased, even if you don't want them to be. Because of this, last year I stopped updating an app using Qt. The higher resolution a display is, the less and less you need anti-aliasing so it's unnecessary in the 4K and up era. Also while I am not on a 4K display, I find AA fonts blurry compared to nice crisp hinted non-AA fonts.

mark-r 5y ago
As you get higher in resolution, I'd expect the difference between AA and non-AA to get less noticeable. Is that not the case?
nyanpasu64 5y ago
What OS and DPI are you on?
jhgb 5y ago
Have you tried Ultimate++, by any chance?

pjmlp 5y ago

WinRT looked great, finally .NET being like Delphi and a C++ stack that looked like C++ Builder, for those moments that .NET alone won't do it. On one side .NET Native is left to stagnate in C# 7, and C++/CX got replaced with C++/WinRT, which to this day (4 years later) still doesn't offer any kind of IDL tooling on VS (lets forget for a second that IDL exists since OLE 1.0), and requires manually merging generated files. Then to top that, we get MAUI on top of WinUI, but with the XAML format used by Xamarin. Anyone following the now 2100+ issues on Github, community calls, change of roadmap of what WinUI 3.0, Reunion and XAML Islands were supposed to be originally, and where they are going after Windows 11 announcement, can only be dismayed. They don't seem to either get the complaints, or most likely, are stuck in a position where they cannot publicly acknowledge them. OS/2 was actually much better than this with CSet++, while SOM had metaclasses and implementation inheritance, with Smalltalk and C++ support. Still, I can equally well rant about other platforms, it is all a matter of which flaws we are willing to put up with.

n8cpdx 5y ago
I think there's a degree of denial. I remember walking up to an engineer on the WinUI team at Build (can't remember if 2018 or 2019) and they were _shocked_ that I had complaints about UWP. They seemed to think it was a revelation. It was honestly offensive how out of touch she was. I think at least the PMs on that team do not understand the human suffering they cause by releasing such a bad product. Anyway, after a particularly awful project involving UWP and Forms UWP, I'm taking my vacation days and using them to learn Typescript, React, and Electron. Edit: if you find yourself working at Microsoft on the WinUI or UWP teams, quitting is an option. There are many good products that could use your skills and programmer labor is in high demand.
- pjmlp 5y ago
  I guess you have put it quite well.