Not so much anymore. The standard deduction for a married couple is now above 30k. It would take a large mortgage to pay that kind of interest in a single year. (Principle is not deductible; only interest)
WinRT is not the same thing as managed .NET code. There is no requirement that a UWP is .NET. There are many examples of unmanaged C++ UWPs, including the open source Windows Terminal.
WinRT is a mechanism to express APIs in a way that is amenable to cross-language usage. It is built on top of COM, and is not a replacement for COM.
Windows Terminal is sort of a clusterfuck of multiple programs, only one of which is a UWP program (the actual visible WinUI shell that runs) which you're not allowed to do as a UWP-era Microsoft Store app, but they got internal permission to do that.
Its now a WinUI 3.x program, apparently, and now the Store no longer requires UWP programs, so WT now only needs to make the "ships inside of Windows release images" guys happy, which apparently is harder than making the UWP-era Store guys happy.
I don’t personally have the time or inclination to do any retrocomputing, but I love seeing the repairs that people do for them. It’s interesting in a way I wouldn’t have expected. Thank you for sharing.
That’s similar to what vcpkg does under the covers. It clones the repo containing the dependency’s source code and then compiles it using the same compiler as the rest of your project. This avoids static libraries and ABI considerations while also avoiding having to copy/paste their entire source tree into your own.
I was personally affected by this, but it did not harm me. The battery drain was obnoxiously high (having to charge 2x a day instead of once every 2-3 days). I am always near a power plug so I was never in much danger of shutdown. However, I can easily imagine how others would be.
I ended up realizing something was odd with the app and tried uninstalling/reinstalling the app to fix it. Which did in fact fix it (at least temporarily).