ZFS is also great for teams that work on ginormous code projects. When I was a contractor at IBM in the 90's we had something similar so we could work on OS/2

ZFS is also great for teams that work on ginormous code projects. When I was a contractor at IBM in the 90's we had something similar so we could work on OS/2 source code. The entire build project was made up of hundreds of other sub projects and it was way too big to fit on a single developer machine of the time. Plus the reality was that individual developers only edited small portions of any part, even though they needed the whole to build and test. In later years, I've found myself thinking about ZFS for other big project scenarios. Like legacy enterprise websites that have gigs of static files and scripts that integrate with parts of webapps, etc. it's a pita to sync an 80gb mirror to every dev and a horrible waste of space. Much more efficient to simply mount the production mirror once and then store small edits locally. Note that these kind of legacy sites are usually not checked into source control because they are too big.