You are aware that the write IOPS of your RAIDZ VDEV is the performance of a SINGLE DISK, right?

I ran a home ZFS box with 2 GB in it (1.5 TB of mirrored storage) for 6 months with zero issues using FreeNAS. It's now got 10 GB, for home media streaming use i have noticed basically zero difference. Saturated gig-e with both setups.

Bullshit. You can add different size VDEVs to a pool, it works fine. It auto balances load across them, and no partitioning is required. My current home setup is 2x1 TB and 2x 512 GB mirrors (soon to be replaced with bigger drives, when it is full).

Just accept that you need to add (or replace) disks 2 at a time (mirror VDEVs), and move on. Unless you're dealing with > 20-30 drives, I'd suggest that RAIDZn is a poor choice. Also, the way writes work, making massive raid groups with large numbers of drives in them (i.e., adding another drive to a RAID5, like you would with BTRFS) is a bad idea. Parity RAID In general is a bad idea. Capacity is cheap, performance is not. Parity raid sucks for performance.

Yup. Most people's expansion difficulties are due to retarded pool configurations. If you accept that 1. disk is cheap and 2. mirrors, whilst expensive in terms of disk capacity are way better performance and more flexible, zfs rocks.

People seem to have it stuck in their head that bigger RAID numbers are better, but RAIDZ/RAIDZ2/RAIDZ3 are only really useful when you're dealing with HUGE numbers of disks and performance is not so important. Normally you're far better off creating a larger number of VDEV mirrors, both in terms of performance and in terms of flexibility.

Which brings up another point - those not used to dealing with enterprise storage may not realize that you can/should/maybe want an array with more than one RAID group in it. They end up putting all their disks in one big VDEV which sucks for performance and flexibility, then blame ZFS for not being flexible.

Read how it works, don't make retarded choices based on ignorance, and you'll be fine.

Think about why you want to do that. Normally, it's due to fuck up from not setting your pool up in a sensible manner in the first place. Don't do that.

1 GB of RAM is worth about $20 these days anyhow (less?).

And yes, de-dup is expensive. Most of the time in my experience you get far better benefits from compression anyhow (source: real world enterprise datasets at work).

CPU and RAM overhead is not "required". If you want to do things like in-line de-dupe, sure. If you use retarded ways of setting up your pools, then sure, expandability sucks.

The rules aren't "wierd", they are just different. The big mistake people make with ZFS is diving into it without reading any of the documentation on the assumption that they know what they're doing because they've used other filesystems before.

Don't do that. Have run ZFS for years, it's awesome.

You know you can lay a zfs filesystem on files, right?

The bit about the Apple Watch GPS being able to tap you differently for left or right is genius. I ride a motorcycle. I have enough to look out for without being glued to a GPS. Left/right haptic feedback to indicate direction on a watch will be awesome.

US has had BS cheap airfares for decades.

Here in Australia you're talking $300-400 to cross the country. And that's a cheap flight.

Media slant - beware. Russians will likely tell you that this is because the humanitarian aid convoy they sent got attacked. Presumably, they are sending more supplies and defending them this time.

Which version is true? Probably the truth is somewhere in the middle. Both sides use propaganda in any confrontation - not just "the bad guys".

OS X is a lot more than a Window manager. The fact that Linux people tend to think they can replicate what OS X is, by building a window manager that looks similar is pretty much representative of the problem. No one bothers to design any of the platform to build things on. Cocoa is massive and full featured. It provides everything you need to build applications, and is used pervasively throughout the system.

This man has claimed shit loads of things that have been pure crap. Do you really need references?

Such as? If you're going to post such things, you need to back them up.

And to clarify - yes you need to open ports on the box, of course to provide services. But there is zero reason that you should be enabling non-user facing traffic to be sent or received to/from the box from end user machines.