SD cards (and CF) are not going to be replaced in cameras any time soon so this new standard provides zero benefit to me,
Except that SD cards are not nearly fast enough for current high megapixel cameras when shooting using RAW. Many higher end cameras have abandoned CF and SD cards and have moved to using XQD due to needing continuous write speeds of 400 MBps or more.
A camera that shoots RAW files around 80 MB (which is what the current crop of high-resolution cameras do - such as the Nikon D800, Canon 5DS, and Sony a7rii) needs at least 400 MBps to maintain a 5 fps burst without needing a very large buffer. Some professional cameras can do up to 10 fps bursts which requires even higher speeds.
Funny. That doesn't seem to have stopped the Hackintosh community from installing El Capitan on their Hacks.
Yes, people have found ways around it like they do for every version. However almost all of the solutions involve some combination of patching the installation to remove the checks and/or software solutions that use UEFI modules to intercept and spoof the results of various hardware checks to trick the OS.
The points is, you cannot simply take a current OS X install drive and get it to boot directly on non Apple hardware without using such tricks and modifications due to the checks done during the boot process.
The Windows 10 ISO is over 6 GB. Thank you for proving that the lynch mob was right!
No it's not. I have the 64-bit Windows 10 build 1511 ISO that has Home and Pro versions and it is slightly less than 3.6 GB.
Even the Enterprise version ISO is only slightly larger at 3.7 GB. Only the ISOs that include both 32-bit and 64-bit versions are larger than that and that is just because that version effectively is two separate install images in a single ISO (the 32-bit and 64-bit installers don't share files).
And once I discovered that output is refomatted depending on destination it was the nail in the coffin.
In Powershell the output is always formatted in the last step of an operation because it is an object-oriented shell and everything is technically an object or array of objects.
Once you understand that everything is an object, the behavior of Powershell makes a lot of sense and you can use the object-oriented nature to do things that would be fairly difficult to do.
If you really want to work with plain text in Powershell, just pipe the output to Out-String which will give you the same text-output that is printed to the console in most cases or ConvertTo-Csv | Out-File for CSV output.
The reason computer chips are so small is computers don't eat much.