I don’t remember any version of Windows I actively use ever auto updating for me either, but that’s because I turned that shit off myself. I had a test VM reboot itself at some point, but it recovered itself perfectly so I only noticed it because the open Firefox tabs all appeared to have unloaded by themselves.
You don’t need to know any programming languages to use Linux, and if you’re a nornal computer user and buy a Mac you don’t need to compile anything either. You’re also free from Microsoft’s stupid advertising and Edge sabotage.
I’ll have you know the reason why my laptop didn’t display over a dock isn’t because of bingbong-SDK, but rather because Linux 6.1 altered a kernel API that evdi 1.14 didn’t support, hence breaking the DisplayLink driver written by Synaptic, thank you very much. But yeah, this stuff does happen occasionally and it sucks. But hey, the problem wasn’t Nvidia’s terrible software for once!
I find it funny how you say it wasn’t bingbong-SDK and then go on to explain what actually happened, and even that could’ve been a satirical comment I would’ve written.
These issues are common for people running bleeding edge Linux like me, it’s just something you accept when you use code that was finished a week ago rather than wait for it to be tested for stability for months like most Windows code.
You don’t get that stuff on Debian/Ubuntu/Mint/Fedora, or course.
I don’t remember any version of Windows I actively use ever auto updating for me either, but that’s because I turned that shit off myself. I had a test VM reboot itself at some point, but it recovered itself perfectly so I only noticed it because the open Firefox tabs all appeared to have unloaded by themselves.
You don’t need to know any programming languages to use Linux, and if you’re a nornal computer user and buy a Mac you don’t need to compile anything either. You’re also free from Microsoft’s stupid advertising and Edge sabotage.
I’ll have you know the reason why my laptop didn’t display over a dock isn’t because of bingbong-SDK, but rather because Linux 6.1 altered a kernel API that evdi 1.14 didn’t support, hence breaking the DisplayLink driver written by Synaptic, thank you very much. But yeah, this stuff does happen occasionally and it sucks. But hey, the problem wasn’t Nvidia’s terrible software for once!
deleted by creator
I find it funny how you say it wasn’t bingbong-SDK and then go on to explain what actually happened, and even that could’ve been a satirical comment I would’ve written.
These issues are common for people running bleeding edge Linux like me, it’s just something you accept when you use code that was finished a week ago rather than wait for it to be tested for stability for months like most Windows code.
You don’t get that stuff on Debian/Ubuntu/Mint/Fedora, or course.