111–120 of 167 posts
Earlier quoted context omitted.
Computers at this level are durable goods and ostensibly help you take an income, so it's not too strange.
Only if you need this much computing power. The typical webdev can probably get away with a quad core AMD/Intel cpu for <$200. Very few people actually need 12+ cores.
Earlier quoted context omitted.
Yeah it has gotten worse. You should run an adblocker on your iOS device.
To add, I recommend Adguard, 1Blocker X, Wipr, or Firefox Focus. Out of those, I believe only 1Blocker X has a cost, although AdGuard has a subscription for DNS privacy and security/custom filters. I personally use 1Blocker X.
Earlier quoted context omitted.
You're comparing apples to oranges. Operating system architectures can vary a lot. CPU architecture between Intel and AMD can't vary much since they both target x86. Every vulnerability found with Intel CPUs can and has been tested for against AMD CPUs which is something you simply cannot do with operating systems, and AMD CPUs have been found not to have the same vulnerabilities.
> CPU architecture between Intel and AMD can't vary much since they both target x86. Completely and utterly false. The exploits being found exist at a point much lower than the x86 instruction set. ARM processors were also hit with speculative execution exploits.
Earlier quoted context omitted.
Nvidia's Linux support? AMD actually has open source drivers these days, just like Intel, Nvidia just gives you a binary module, which means in order to make use of that hardware you have to taint your kernel and aren't free to update it if the in-kernel ABI changes. It's basically on par with the vendors of all those "useless ARM devices out there", none of them with "usable Linux support".
AMD is finally approaching parity in the past year or two, but Nvidia is still ahead in terms of day-to-day usability. It sucks that they're closed, but if you just want to install a driver and have your system work, Nvidia is ahead. Look at this mess: https://wiki.archlinux.org/index.php/Xorg#AMD Do you want AMDGPU, AMDGPU PRO, ATI, or Catalyst? How do you choose? Let's assume you want open source and recent, so pro…
1) Closed driver
2) Weird incompatible multimonitor support called twinview? Where windows would maximize to stretch across all your screens
3) Abusive on the PCI subsystem, so that my sound hardware would experience underruns, both spurious and reproducible events such as during workspace switches
4) Lockups
5) Corruption/lockups switching between FB terminals and the X terminal
I switched to ATI and the open source driver and all these problems went away.
Earlier quoted context omitted.
Computers are quite durable these days. You can easily run a useful, general-purpose OS on a computer from 10 years ago and perhaps more, even one with baseline specs. If that's not enough to be considered a 'durable good', I don't know what is.
Tell that to my 9 year old iMac with the dead GPU that I can't replace, won't start up, and is going straight into the trash. Never again, Apple.
Earlier quoted context omitted.
More like this, intel has cut a lot of corners for a long time in their x86 processors, mostly to have better performance, which ended up with all these vulnerabilites we keep hearing about every couple of months. They're just now suffering the consequences of all the shady things they've done to try and establish a monopoly in the CPU market
A more generous interpretation: Intel made decisions that favored actual measurable performance today at the expensive of theoretically known vulnerabilities that might be exploited in some hypothetical future . They gave the market what the market demanded at a cost they tolerated. And even now, after said theoretical vulnerabilities have been reified, there is very little cause to be concerned about the vulnerabili…
Earlier quoted context omitted.
Does MST even work 4k@60 over DP? 4k@60 requires so much bandwidth, that is uses both MST channels (it is internally handled as two monitors); if you want to use both channels separately, you are stuck with 4k@30 at most.
Yes, MST absolutely can do 4k at 60hz. This is what the first Dell 32" 4k used. My rMBP has been able to do this since February, 2014. I was trying to get my RX 560 in mid 2018 to do this and it just was not possible via any means with Ubuntu 18.04. I ended up using an Nvidia 1040 with the binary drivers without issue. The nouveau driver for the 1040 was able to do it with a newer kernel than Ubuntu 18.04 had (I was…
Earlier quoted context omitted.
Mesa drivers are fine. The one with horrid performance is their proprietary AMDGPU-PRO, but there's no reason to use it. (especially since Mesa now support GL compatibility profile)
Mesa drivers are far from fine, they only got rid of the "core only" braindead schism just last year (IIRC) and that was thanks to pressure from AMD to get games working. Even then a lot of Mesa's codepaths are downright awful. Nvidia had OpenGL as a major focus for decades (it was even the first API to get new features introduced in their hardware via extensions - though nowadays they also seem to do the same with V…
And as to compatibility context, IMO OpenGL shouldn't have defined it at all. It is rather weird to have rendering code using both legacy fixed pipeline and modern shaders. From my experience it just causes problems everywhere, and I had encountered unexpectedly bad performance and glitches on Nvidia drivers too. (though maybe less often than on Intel/AMD)
Earlier quoted context omitted.
> CPU architecture between Intel and AMD can't vary much since they both target x86. Completely and utterly false. The exploits being found exist at a point much lower than the x86 instruction set. ARM processors were also hit with speculative execution exploits.
You're focusing on something that doesn't really matter in the context of what he was saying, and ignoring the bigger truth which is that security researchers DID look at AMD processors and they DID find that they do not suffer from the vulnerabilities that plague Intel.
And, his point still stands. While intel has/had meltdown, which was pretty bad. That doesn't mean that a Meltdown like bug doesn't exist in AMD's hardware.
It's like finding a bug in the OpenJDK that isn't in Zulu and then declaring that "Zulu is more secure than the OpenJDK!"
Or an even closer example "Intel doesn't have the TLB bug[0]! Intel makes better CPUs!"
AMD isn't guaranteed free of all exploits. It is only guaranteed to not suffer specifically from meltdown.
Earlier quoted context omitted.
A more generous interpretation: Intel made decisions that favored actual measurable performance today at the expensive of theoretically known vulnerabilities that might be exploited in some hypothetical future . They gave the market what the market demanded at a cost they tolerated. And even now, after said theoretical vulnerabilities have been reified, there is very little cause to be concerned about the vulnerabili…
Any security researcher or engineer worth their salary is already planning for those theoretical vulnerabilities. Ideas like these are hashed out at the development meeting. Not fixed after the cart has left the barn.