Now,
https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynami...
> For the purpose of complying with the LGPL (any extant version: v2, v2.1 or v3):
> If you statically link against an LGPLed library, you _must_ also provide your application in _an object_ (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application.
Basically not a single software developer is going to go through these hoops to link with LGPL statically. I don't care about theory crafting. Linux has been there for over 30 years now. Show me the applications that comply with that. I dare you.
Actually I know a single example (!) and that's proprietary NVIDIA drivers. Not an application BTW. You cannot imagine how difficult Linux kernel developers have made life for NVIDIA. Yeah, there's a huge object file to be linked with the kernel. Other examples? None. In Windows you compile a driver and have it work flawlessly for at least a decade.
Sorry, I'm done with you. You're now baselessly and shamelessly accusing me of lying where a simple Google search reveals everything I say is true.
Windows requires none of this crap. What's funny is that Win32 is the only stable Linux API. Not even glibc provides it. What's even more funnier is that DirectX is still a far more richer set of APIs than what Linux provides despite Open Source making it as hard as possible to link to it. And basically no one does.
With most laptops and pre-assembled PCs Windows comes for "free" (included in the cost). If you're a builder, you can get a Windows license for a low as $10 and live happily ever after and use your old applications including I don't know Adobe Photoshop CS2 released ... almost 20 years ago. Still works fine in Windows 11.
Merry Christmas.