The point is that anyone with the technical skills to break WPA2/WPS is going to be able to spoof their MAC address. Ergo, if you're using WPA2, you don't need a MAC filter because anyone trying to break it will likely already be spoofing their MAC address

That attack is related to clients who are already authed. WPA2 authentication has not been broken, AFAIK.

Why not? Compilation is just converting data into more data that is afterward executed as code. It would make JIT a lot harder, if not impossible, however.

I'm not sure that's entirely true. Primitive types in Java and value types (including structs) in C# are by-value. I may be showing my inexperience here, but why would you want to allocate a value type on the heap? And does it even matter, given that value types are passed on the stack anyway?

s/useless/cumbersome

It's more that if you can't prevent the decrypted stream from being recorded, your DRM is useless.

Last I heard, the iPad had well over 80% of the tablet marketshare in the US

MP3 does not include any form of DRM. Sure, any MP3 player that supports PlaysForSure or iTunes has some for of DRM on it, but mine does not support either.

I'm pretty sure this is false. Memory protection prevents programs writing to another application's memory space. That's providing data integrity, and in no way prevents copying.

Even on "tee-resistant" systems there is always the analogue hole.

I don't think you understand asymmetric encryption. You need the "secret" key to decrypt data. The public key is not secret and is only used to encrypt data. DRM require the user to have the "secret" private key on their computer, but not have any form of access to it themselves, and no way to capture the decrypted data.

Does Microsoft actually advertise that it has 64GB of storage space? Or do they advertise that it has a 64GB SSD? Whether it's misleading or not is another question, but I don't believe it's false advertising.

And when my computer boots, it will say it has 4.294967296 GB of RAM. Honestly, it makes more sense to me to use GiB, as stupid as it sounds, for the rare occasions where it makes more sense (like memory addressing)

Right, and we should still be using feet over meters and gallons over liters, etc.

What GP is suggesting is that RAM and RAM only should be referred to in sizes of MiB, GiB, etc. as it makes no sense to apply KiB to network transfer rates or hard disk storage space (although it does work for SSDs).