Omeed
Can't see a way to get around this bug in pure Swift. Anything besides simply initing the struct seems to cause a crash at runtime. This affects the `System.uname()` method....
Should be an improvement over the raw I/O Kit calls, less prone to break, and more general (support for desktops).
Rather than the classic -1, 0, etc. that can be confusing and inconsistent, optionals would be clearer and more _"Swifty"_.
- As seen in [Activity Monitor](http://en.wikipedia.org/wiki/Activity_Monitor) - Seems to be a custom calculation, no API for it - Maybe something in IOPMLib
- For listing all of them - All ops in Activity Monitor - Process ID - User - % CPU - # Threads - # Ports - Real Memory -...
- Everything should be the same for the most part (32-bit devices are many though - vm stats) - Need cert to test
- As a reminder to factor this in (I/O Kit) - It may be there's nothing we have to do. The burden is really on the client with having a...