Earlier quoted context omitted.
There's a reason Microsoft is aggressively deprecating "older" CPU's that work perfectly fine. Heck, I have one laptop with Windows 11 that worked great, but won't update from 22h2 to 24h2 because CPU support was dropped between versions, leaving me with only the glib suggestion from the Windows Update UI to "Buy a new device". Ironically, installing Windows 10 and activating ESU would lead to longer hardware life. O…
TPM wasn't the only reason older CPUs were dropped. The biggest reasons where the line in the sand Microsoft chose would not be supported in Windows 11 was Spectre/Meltdown [0] mitigation. Windows 10 added a bunch of intentional slowdowns to mitigate that disaster and people incorrectly blamed Windows 10 for being slow and not the CPUs and their CVEs. Windows 11 seems to have wanted a clean slate without needing to h…
Retiring Windows 10 and Microsoft's move towards a surveillance state
431–440 of 514 posts
Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#432Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#433IT & software dev for a small-midsize company. I wasn't able to finish migrating last month due to a pressing project, but we're migrating almost all of our systems at work to Linux. 90% of our user's work is done in a browser, and the other 10% is in an in-house application I wrote. That app works on Linux, since my work machine has been on Linux for years. We'll have a few macs and 2 win11 machines, but the rest ar…
Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#434Earlier quoted context omitted.
> I would say that specifically with Secure Boot, Microsoft actually promoted user choice: A Windows Logo compliant PC needs to have Microsoft's root of trust installed by default. Microsoft could have stopped there, but they didn't. This was not the case with the initial rollout of Secure Boot, it was combined with locked BIOS to lock PCs so that they could only boot Windows 8 on some devices. This was the case on W…
> This was not the case with the initial rollout of Secure Boot, it was combined with locked BIOS to lock PCs so that they could only boot Windows 8 on some devices. This was the case on Windows RT ARM machines from that era. Okay, but, that was like 15 years ago, on some shitty first-run computers that no one bought. A failed first attempt. I've never met a single person that owned, or has ever used, a Windows RT de…
Some combination of the advertising industry and those with a vested interest in anti-fraud such as banks will eventually try to sneak remote attestation in there, which has the potential to put a complete end to ownership of devices as we have always understood it.
Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#435Earlier quoted context omitted.
Right-click requiring two clicks to get to the options you most likely want to use (e.g. 7z unzip or opening in a specific program) This one you can still change. It is some hidden registry tweak, but there is the capacity to always "show more options".
Changing the registry is far too much of a hurdle.
Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#436I should mention that ubuntu phones home a lot. I like the fact that it has done a lot for the linux ecosystem, but there are a few things: - it has a privacy policy - it forces updates - their hardwired package ubuntu-advantage-tools cannot be uninstalled without breaking the os - motd has telemetry and nags - can't disable snaps - whoopsie uploads crashes to canonical now, this is different from windows because the…
Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#437Earlier quoted context omitted.
Not really. On linux, you have OpenSCAD (which is okay for some applications) and you have FreeCAD (which sucks imo). Right now, I just use OnShape which works in my web browser and is similar to SOLIDWORKS (and it's $0 for students). In the future I will try running windows CAD under linux using kvm and this: https://github.com/casualsnek/cassowary
Just use Windows lol
Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#438Earlier quoted context omitted.
TPM wasn't the only reason older CPUs were dropped. The biggest reasons where the line in the sand Microsoft chose would not be supported in Windows 11 was Spectre/Meltdown [0] mitigation. Windows 10 added a bunch of intentional slowdowns to mitigate that disaster and people incorrectly blamed Windows 10 for being slow and not the CPUs and their CVEs. Windows 11 seems to have wanted a clean slate without needing to h…
Yes, Microsoft is blocking CPUs which lack the ability for Virtualization Based Security. Given OS security is important to Microsoft (surprise, I know), enforcing VBS is a priority.
Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#439Earlier quoted context omitted.
Just run it in a windows vm for just that use, there's great ways to make this almost seamless in linux. works better than win/etc.
CAD applications usually require graphics acceleration. I've tried to make Fusion 360 work on linux using VMware, VirtualBox and GNOME Boxes – performance was unacceptably bad.
Re: Retiring Windows 10 and Microsoft's move towards a surveillance state
#440Earlier quoted context omitted.
Make sure libreoffice is included, and ublock origin. Show them how much faster it is, with fewer ads, and no subscription to Microsoft required just to write a document. The business customers might want to know that databases are a lot cheaper on Linux, especially for small business. Literally spoke to an automation company the other week that told me "we have to delete a bunch of stuff every time the database gets…
> Make sure libreoffice is included Probably an unpopular thing to say here, but in my experience pushing non-tech people to use libreoffice as part of a Linux transition is a fast track to getting them to hate Linux. Using Google Docs has been much more welcoming in my experience. Something about libreoffice doesn’t resonate with a lot of non-tech people.
My understanding is that the issue is the way OO/LO and the OS work together to handle file writes, which will not be changed because Linux distros do it right and Windows does it wrong and too bad that I was trying to use OO on a Windows PC. But I can't get a straight answer, and even if I were to, it wouldn't fix the bug - because the bug would be that I was using Windows. And now that I know that this is something that happens, I don't have any real guarantee that tomorrow the problem won't be the particular distro that I use, or whatever weird personal ax-to-grind led to the design decision that would now be giving me a headache. And that probably goes doubly for your average Windows user who doesn't really know what they're getting into.
Obviously, Google's support situation isn't any better. They've also had their share of catastrophic data loss fun-times. I genuinely don't know what the answer is.