OTOH, it would probably work just fine shutting out a wardriver or any non-tech-oriented neighborhood mooch.
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
Of course at the fundamental level, you don't want to do that, because you would take away the possibility to compile programs.
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.
You don't need Java or C# (and all their inefficiencies such as the GC and "allocate everything on heap")
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?
And yet it is so useless without the concept of destructors.
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.
Computers also have memory protection which prevents an application from copying data from another application.
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.