XenosTech

Windows Defender is definitely the best at not bugging you to buy a paid version
 
Because you already spent $90+ on a Windows License

Symantec: The AV that used all of my laptops 512MB of RAM. And wanted even more.

I'd still rather use Defender than Symantec though, they earned my hatred many times lol

It's even worse when they not only do they refuse to repair it but they are doing them damnedest to not let anyone else do it either.  That is the very definition of anti-consumer.

That really is another important thing here which we all saw with Linus' iMac Pro troubles -even if it is genuinely out of warranty, or if the damage was something they wouldn't cover, like the user dropped it in a lake, etc. - you should have the option to pay for reasonably priced first party repairs.  Not only do they all too often refuse to honour the warranty and/or overcharge for repairs they are willing to make, they straight up don't offer the option far more than they should.  If it was genuinely a write off because it was run over by a truck and the body, screen, CPU, motherboard, etc. were all snapped in half, sure, I can understand them recommending a full replacement, but they do that when the repairs necessary are actually quite doable and certainly less than the cost of a full new machine.

I understand that PCs also have an equivalent of the T2 chip and losing it means losing the data, and that that's expected behaviour.  I understand that it's only ever as good as the password, and the encryption algorithm used.  I understand that without the password, it should be impossible to get in.
 
Perhaps I should clarify and reiterate my point: last I checked, there's encryption methods that don't rely on such a chip that would take even a super computer multiple heat deaths of the universe to brute force, thus making something like this unnecessary.  Are you saying this is not true and all modern encryption is basically pointless?
 
Specifically in regard to these machines, it's worse than a controller failing because even if that isn't dead, if there's some other issue with the machine that makes it inoperable, which seem to happen fairly often, you're still basically out of luck because the drive is soldered in and fed through that chip, so your data has to go through the machine.
 
I'll also reiterate that on top of and aside from all this, even if for the sake of argument we accept that this is a good and reasonable system for maximum security, I would argue that it's definitely not the ideal system for the majority of users.  If you require top tier security at the cost of having this risk, you can be glad the option exists, but to have it on by default for people who probably don't even realize it's there, why they should care, or that it means their data dies with the machine and who are used to the option of having it recovered seems like a very poor choice.

Encryption is great when I have control over it. When Apple has that control and I don't, it's not. That's more like a mafia protection racket; you pay them to "protect" you but at any point they could just screw you over because they feel like it. Your data is held for ransom for pretty much no reason - there is no reason you couldn't just use a password or other methods you can directly influence and access even if the machine doesn't work anymore.

I can't help but point out this is exactly the core point of the video.  People can whine all they want (and more often than not when it comes to Apple they don't even do that much) but ultimately all that matters at the end of the day is if they buy it or not, and if they do, there's no reason for Apple to change, and you have to accept whatever experience you get at that point because you went in fully informed and knew what you were getting.

Irretrievable data and being at the mercy of apple for all repairs is just another reason never to buy such a computer.    Plenty of more than adequate alternatives out there.
 
 

I'm only getting a new system cause my friend can't afford to buy a new one so I'm selling him this with my 1080 and another kit of ram on the cheap

Welp glad I went with a 1080Ti over any of the RTX cards

I'd say both yes and no. People follow the path of least resistance. Developers might think twice about being lazy and just sticking to 32 bit if it requires them to do extra work to support the application(s) versus migrating to 64 bit going forward. I get the feeling that many people just do things because that's how they've always done them hence we still have apps relying on 32 bit libraries to this day (not counting unsupported legacy apps). If 32 bit is absolutely necessary then you'll just have to work around it otherwise just fix your stuff and transition to 64 bit.

F35 - GDPR Edition

Sony wx1000mk3 and b and o h6 or h7 or h4

Lol that’s true. 

I don’t have a new enough phone that I need a lot of dongles (iPhone SE's got a headphone jack) but with all my other tech, I’ve gotta use a stupid dongle.

My daily drivers are Corsair HS60s, little big and bulky and they do get hot after while but they were cheap, and they’ve got awesome sound for the price.

Sigh and I do love me a good pair of wired ones lol I was contemplating buying a mp3 player and sticking my 128gb mem card in it and calling it a day. I'd charge my phone less that way too

Just don't get a pair of headphones with high impedance because your phone wont be able to run them. Anything less than 80ohms should be good.
       

It really is a pain. We have truly entered into the "age of dongles"...

Try Bose QuietComfort 25 if you dont want to go with sony again.

Actually forgot about that.

true but only half, epyc and threadripper use one die from ryzen and one that has its bottom layers mirrored to allow fro shorter connections between the dies 

I'll take 5 and a box of cranberry juice

I'll take 5 and a box of cranberry juice

I can try, though truth be told I don't understand much about them. That being said, I can certainly point out which have yielded the most performance benefits from my personal tests. This guide is mostly comprised of trial and error, with most of the terminology coming from those that taught me most of what I know about memory overclocking. 
 
The funny part is that I looked back at this guide and completely forgot to add the Ryzen part, despite buying my Ryzen components well over a year ago. I guess the silver lining is that it might come in handy for Ryzen 3000.

I'll take 5 and a box of cranberry juice