Hmm I was in a rush and didn't check if the link had the info I wanted.... oh well. Well this link is someone complaining about startup time. But windows 8 apps actually run
slower not just starting up. This is because microsoft couldn't find a team to have metro apps use COM: https://msdn.microsoft.com/en-us/librar ... 85%29.aspx
Small history lesson:
COM came out maybe about 15 years ago. It set out to solve the problem that because Windows now supports x86 processors (private application memory space). Embedding/Using feign code was close to impossible. That is until COM came out. COM, at the time, was a super powerful tool but was awful to use. Few learned how to use it.
Now back to present:
So no one knows/remembers/wants to use COM. It, again, is a huge pain in the *ss and is in a way rocket science to use. So one thing that Microsoft needed badly when making metro was COM programmers to be able to interface directly with the OS and with graphics, etc. This same work has already been done for Win32 target but it needed to be done again for Metro. Well, ironically, Microsoft couldn't find a team who knew how to use Microsoft's own technology. So how did Microsoft even make the Metro development target? Essentially, the Metro interface is analogous to a web browser. It functions in just the same way. NOTHING is direct. What about DirectX11? Nope. You actually don't interface directly with the graphics card.
That is why it is slower. Microsoft couldn't find people who knew how to interface directly with their own OS. It isn't their fault exactly. They just are pretty stubborn about supporting old technologies...
This is why I use Arch Linux.
EDIT: Unfortunately, I cannot find where I read about this :\