Some people don't realize that even business grade is statistically multiplexed and not "dedicated" in the overly strict sense of not shared.

MP3 causes me physical pain in my ears for certain types of music that OGG does just fine. Feels like I have an ear ache with a bunch of pressure that eventually turns into a migraine if continued. MP3 is crap.

Windows is limited to 512 total shadow copies. Shadow copies could accidentally be lost for a number of reasons, they are not guaranteed. Microsoft has a list of things to be careful about that can influence your chance of losing a shadow copy, including block size and defragmentation, which could cause older shadow copies to get destroyed.

LVM has performance issues. Many people complaints of over 10x reduction in performance after only a few snapshots. It also only works at the block level and not the FS level, which highly limits its usefulness.

For most people ZFS could be considered a "back up" solution to a certain extent and making certain assumptions. For a large enterprise systems, never rely on a single file system. The data files should be replicated to multiple systems that use multiple file systems.

I saw a ZFS benchmark comparing random read, write, read+write, and sequential read, write, and read+write of a 15k RPM RAID and 5400 RPM with 10x as much storage but just as many spindles for a fraction the price, and the 5400 RPM setup was faster once the 64GB of SSDs got warmed up.

PC-BSD is just a thin wrapper of scripts, wizards, and some decent tools over FreeBSD. You can upgrade and downgrade to/from PC-BSD/FreeBSD.

HardenedBSD was forked with the explicit idea of testing new security ideas and seeing what works, then pushing the code upstream back to FreeBSD. *BSD is not like Linux distros where they rarely work together. A lot of security ideas require some major changes that would not be feasible as a simple branch.

Ohh, you mean segfault when you read unallocated memory? Even if you could, are you planning to read all 8,589,934,592GiB of the address space? with O(n) scaling, assuming a crazy low 1 clock cycle per address, it would take you about 35 years to scan the entire 2^63 user virtual address space at 4ghz.

I am not saying ASLR is perfect, I'm just saying it's not nearly as simple as you make it out to be.

OpenBSD has an entirely different kernel at this point. Their only major commonality is starting from the same OS a long time ago.

1993 - NetBSD forks 4.3BSD
1993 - FreeBSD forks 4.4BSD
1996 - OpenBSD forks NetBSD 1.0

As much as they still shared code, they have diverged over the past 20 years.

They have great documentation, especially compared to the competition, but there are some pieces that are lacking. There is a dedicated group that started in the past few years that is going over documenting the entirety of FreeBSD with people with great documentation skills and are also normalizing the formats to a new document format. Large undertaking.

My cousin used ZFS+gluster for this multi-petabyte system.

ISPs tat can do transparent HTTPS proxying? Cool, they've broken HTTPS or hacked your computers.

Overhead is only about 5% with 1500mtu. Doubling your frame size won't do crap. SANs love larger frames so frames can be the same size as disk sectors, but they are special compared to normal internet data transfers.

Suburban densities are optimal. It costs most per customer to install fiber in a big city than a medium city. Tearing up concrete and drilling holes through large many story apartment buildings is much more labor intensive than drilling a hole into someone's basement.