Conversation
Notices
-
Embed this notice
Is it a stupid claim to make that i believe there is a secret division inside microsoft set to develop vulnerabilities that way consumers have an incentive to upgrade to their new product?
-
Embed this notice
@waff It is a stupid claim, as they're so incompetent that they don't need a secret division to implement vulnerabilities - their garbage build systems and refusal to allow programmers to fix bugs is more than enough.
It's a proven fact that every time microsoft learns of a vulnerability they report it to the NSA immediately and then think about whether they'll fix it.
microsoft tends to force downgrades onto people, as a result there is no incentive needed to force people to update.
-
Embed this notice
@waff @sally AMD64 has replaced x86 long ago.
Most Aarch64 SoC's use u-boot as their bootloader, thus it's really a matter of enforcing the GPLv2's requirement for installation information.
As for GNU/Linux support, it's a matter of enforcing the GPLv2's requirement for source code and installation information for Linux and enforcing the GPLv{2,3} for GNU software and people will be able to add support for that SoC.
-
Embed this notice
@sally its gonna get worse when or if arm replaces x86, as most of the architecture is known for not having any bootloader or having a very difficult to unlock one and most chips are soldered to boards.
-
Embed this notice
@waff
Doubt, but it wouldn't surprise me. What I do think they do is research and document vulnerabilities that no one but themselves and three letter glowies know so that they can get away with abusing the general public even when the law doesn't allow them to. New computers come with digital handcuffs baked into the motherboard software and CPUs to enforce installing whatever they want on user's machines, and if they don't have a setup that pleases Microshit's masters Windows can simply refuse to boot or work properly, and given the monopoly they have, a lot of stupid and uneducated people relies on Windows to get shit done, so either they comply or they loose their jobs.
-
Embed this notice
@waff @sally I would suggest just writing x64 or AMD64, as x86 is long legacy.
-
Embed this notice
@Suiseiseki @sally when I am referring to x86 i am referring to both x86 and x86_64