> tfw I'm never ever going to buy an AMD no matter how far Intel lags behind
this is customer loyalty, I'm not gonna risk infecting my system with a virus because AMD minimum wage workers fucked up the coding
> tfw I'm never ever going to buy an AMD no matter how far Intel lags behind
this is customer loyalty, I'm not gonna risk infecting my system with a virus because AMD minimum wage workers fucked up the coding
Other urls found in this thread:
lists.debian.org
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
twitter.com
Here's a (You), hopefully the only one you get.
You're not even trying are you
I have unironically never bought an AMD cpu.
They are unreliable. They have bugs in it. (proven). They dont have a GPU. This alone makes Intel better priced. Intel has much better software packages for developers.
>proven
lol
>not having an iGPU is worse
More room for actual CPU.
>better software
???
Reminder that they actually get paid for this
AMD is shit
>Intel never has microcode bugs!
Fuxking kek.
You're fired, Rajeesh.
debian isnt related to intel
>that damage control
>he supports the inability to choose a cpu without a igpu
>he supports to literally bloat up a cpu by ~40%
>Jun 19, 2017
yep, keep using that old benchmark
>i don't want to get a virus because someone fucked me at the hardware level
>therefore I'll use a chip that's fucked at the hardware level
Silent Bob Is Silent. Google it, it's an exploit on Intel chipsets. Sage for baitfaggotry.
The flaw was discovered by some Ocaml people and Debian is merely reporting on it. It's a microcode bug which Intel recognized and patched.
Here, have some more:
intel.com
Check out the errata section. 43 pages of bugs, many of which list "none identified" for the workaround, which basically means "we aren't fixing it, so don't do this".
Reminder to report shitposters.
>Rajeesh
I'm João you shitskin
>not just volume dumping
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
>dual streaming benchmark
WOAH what a realistic benchmark
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
intel.com
DELEEEEEEEEEEEEEEEEEEEEET
What the fuck is "dual-streaming" ???
Prolly some dumb way to rig ryzen's perf.
I remember when a site was doing 480p encoding on i3 vs 8350, with some old single thread algorithm and they were like "look pilldriver is not even good at encoding"
The ways those shill find every day to trick readers is suprising.
tell me when AMD has a dual cpu platform that doesn't suck
allegedly most ryzen's will OC up to 4ghz
if I was building a budget system now I'd definitely go with the ryzen
The better binned ones are starting to hit 4.1ghz now
>They have bugs in it. (proven).
My Intel Xeon would like to have a word with you (TSX bug). My Pentium (F00F bug) would like to have a word with you as well.
Jesus Christ user. I was trying to force a reality check, not make op kill himself.
Thats called threadripper and its sole purpose is to fuck Intel raw.