In a sense, they were partially right, while being wrong. Based on Puget’s data, it’s apparent that motherboard vendors overly aggressive default settings helped contribute to the issue being so prominent, when reasonable settings would fail at a lower rate than comparable zen CPUs.
Obviously Intel messed up badly, and those settings shouldn’t result in this behavior, but maybe this will convince system integrators to have more reasonable defaults in the future.
In a top end system, we’re already sitting in territory where our GPU is our benchmark, do we really need to default to giving the cpu so much power?
Ironically, I’ve just started asking LLMs to summarize paywalled content, and if it doesn’t answer my question I’ll check web archives or ask it for the full articles text.
While I’d never personally use Chrome, you can describe this in another way too.
“Chrome supports draft standards like webUSB, which more and more hardware tools and platforms have started to adopt to enable being able to support users regardless of platform, without needing to design native apps for them.”
You can argue this is good in other ways too, it means that instead of a potentially invasive hardware application for something you might configure or update once, you are using something heavily sandboxed that has to request permissions for anything outside the normal. Another benefit is that depending on what the hardware device is, suddenly these hardware devices can be configured on platforms like Linux and FreeBSD, where vendors are much less inclined to support or cater to natively.
Say what you want about draft standards, but Firefox not playing ball and adopting commonly used ones is a massive miss on its part that hurts its ability to be competitive.
PCIe issues are only really a thing with BCLK overclocking on systems that lack a secondary external clock generator. BCLK overclocking is a pretty uncommon practice that isn’t practical for day to day usage.
With the hacker comment, in fairness the weakest link in a lot of orgs is often the human one. Ignoring obvious stuff like phishing links, people can be disillusioned by their employer or their government through propaganda and other campaigns run by their adversaries. The westerners who supported ISIS, etc didn’t just do so in a vacuum out of the blue.
While you’re probably right, this isn’t super relevant. From Google’s perspective, they just want to auction off the advertising slot and get that view, the actual click through rate on that ad is a secondary issue.
In fairness, the GT 730 will reach 10 years old in only 6 more months and loses performance wise to even older laptop iGPUs by a decent margin. The card alone is years past the age range GPUs “typically fail”, even Windows has long dropped support for it. Expecting even open source volunteers to maintain support for every old GPU while continuously improving the drivers and adding more functionality and fixes is a bit much.
Blocks of numbers moving from mobile to voip, sometimes things aren’t instantly updated in databases and might take a little bit before that eventually happens.
This isn’t something casually identified with flashy software solutions or APIs, it’s more of a relationships with carriers and other companies in the telco space sorta thing. It gets even more fun when you start looking in to MO and MT on the SMPP side of things.
They don’t do so super well, in general. There’s a reason that risk scoring solutions for phone numbers often see numbers flagged as VOIP as red flags.
Typically, people who are trying to defend themselves from nation state threat actors aren’t using iPhones or stock Android phones, and absolutely wouldn’t use safe browsing if they did.
A lot of this land and property is privately owned by the royal family but leased to the government, I’m not exactly versed in UK law; but a governmental attempt to seize a private citizens land seems like it wouldn’t be the smoothest thing to attempt to pull off.
At my current company we’re in an awkward situation with python 2.7.1 and 2.7.5, I’ve found that a easy solution to circular dependencies caused by the new resolver is installing pip==20.2.4 and an older setuptools (I don’t have this version memorized) before doing anything.
Obviously Intel messed up badly, and those settings shouldn’t result in this behavior, but maybe this will convince system integrators to have more reasonable defaults in the future.
In a top end system, we’re already sitting in territory where our GPU is our benchmark, do we really need to default to giving the cpu so much power?