The problem with DLLs are that there are many versions of the same DLL that often need to run at the same time. Which means that you can substitute one version for another, and hijack a program. Nothing new here.
If only it were as benign as that. You can even inject DLLs into a system process, and then have code executed as that process unless things have changed dramatically in the past 4 years.
Are you suggesting that Windows makes a toy computer? Wouldn't a toy GUI consist mostly of big colored squares, dumbed down applications, and a supervisor monitoring your usage patterns?
And I present
Lossless audio CD rip averages 350MB. DVDs usually run between 4-8GB ripped and compress to about 2GB on average. OTA HD average about 12-14Mbps streams, average about 7GB / hr. BD movies at 32Mbps, average about 30GB for 100 min.
It's not as simple as how many flops can you do.
This is why I quoted 3 sets of tests. The Top500 is pretty much flops focused, a very specific test for a very specific workload, which is what all supercomputers were originally targeting back when that benchmark started. While Intel can compete in this arena, as soon as you move to what we might call more realistic workloads, Intel's weaknesses spring out everywhere. You speak of latency - Intel's x86 base architecture has huge issues with process/thread switching compared to any of the RISC entries. Those effects are what kill Intel in the Graph500 list. The Green500 is just a bonus for showing how horrible these processors are, yet as of today, they are the most likely hardware most of us will run. It's kind of like being tied to the current set of inherently dangerous nuclear reactors when a better design has existed for decades, but no one wants to spend the extra cash to get one operational.
AMD also suffers from the process/thread switching costs as originally they were x86 based and I'll be honest that I've not kept up with what they've done since the developed their RISC like core, so can't comment on to what extend they're suffering from those effects today.
A well developed & deployed os+compiler
well, that answers the question about Windows portability....
Do you think the hills in China really look all that different from the hills of Nebraska?
Depends, even hills in one part of Nebraska can look look different than in other parts, provided Nebraska actually has "hills"
IOn the software side of things, Microsoft can force people to Windows 10, but Intel can't force people to, say, go from i3 to i5.
I think that's why Intel has partnered with MS on Windows 10 with the hardware statements. Intel will be sure to mod the CPUs, making older version obsolete, forcing new OS/Hardware cycles. It's going to happen, you just know it.
The person who's taking you to lunch has no intention of paying.