this post was submitted on 19 Jul 2024
868 points (98.9% liked)

Memes

50640 readers
607 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 6 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] CalcProgrammer1@lemmy.ml 54 points 10 months ago (2 children)

Should have not trusted a third party to install proprietary code into the kernel. It's not a Windows issue directly, they have a Linux version too, but anything that allows third parties to put proprietary code into your kernel and automatically update it without your approval is untrustworthy.

[–] SatansMaggotyCumFart@lemmy.world 25 points 10 months ago (1 children)
[–] CalcProgrammer1@lemmy.ml 27 points 10 months ago

I can't disagree with you there.

[–] Damage@slrpnk.net 5 points 10 months ago (3 children)

They have a Linux version, but this happened only to the Windows one... Coincidence?!

[–] qjkxbmwvz@startrek.website 16 points 10 months ago (1 children)

Probably coincidence? It sounds (???) like this is a pretty simple fix on Windows.

The number of times I have borked my Linux machines so they wouldn't boot is, well, greater than zero for sure. Any operating system can be bricked to the point of requiring manual intervention by software with elevated privileges.

[–] Rentlar@lemmy.ca 5 points 10 months ago
[–] CalcProgrammer1@lemmy.ml 4 points 10 months ago

Yes, coincidence.

It's not like they haven't caused Linux outages in the past.