If you want per-application snapshots then you want the application to be in charge of the snapshots - not the file system. The file system does not know when an application is finished making changes to a file. Possibly many files must be changed - the file system does not know so it can not make any assumptions. Applications should be in charge of their own document snapshots using some form of version control. If one wanted they should script it so that a ZFS snapshot was generated - but you are better of using git.
With regards to ZFS, the snapshots are generally done at whatever frequency is defined by the administrator. 5min, 30min, 1day - whatever they decide. The snapshots are accessed from the root ".zfs/snapshots/named_snapshot" directory. There is no piecing together of files - the full file-system, as it was at the point in time it was captured, is available in the directory. The snapshots are immutable - the contents will never change so long as the snapshot exists.
It is more likely that Apple designed USB-C at the same time they designed the Lightning connector. They opted for the Lightning connector and decided to gift USB-C. It is in Apple's best interest for USB to have a good connector.
Looking at how horrible the USB3 connectors are, it all makes sense. USB 3.1 was announced far to quickly for it to have been planned at the time USB 3.0 was being specified. And there was no design debate - the new connector was basically just announced. Looks like someone delivered a fully developed USB-C connector to the USB standard committee and it was enough of an improvement to warrant a new version.
Bottom line: Encourage people to replace clunkers and keep their vehicle well-maintained.
In Japan, this is exactly what is done. Insurance rates increase once your car is beyond a certain age. You do not see many old cars driving around because they cost more to operate then newer vehicles. At lest this is what my Japanese co-worker had to say.
A two-body bullet? Impressive. Thanks for the link.
If they are using a two-body bullet then there are plenty of ways they could control it. For example, directing a slow burn solid fuel "jet".
I was using v2 of the router but that should not make a difference. Apple devices use multicast DNS for device discovery. I found that the router would not bridge mDNS packets between the wired and wireless domains. They would at first but eventually they cut out. This can prevent your iPhone from talking with your AppleTV. From the user's perspective, the iPhone is at fault when in reality it is the network.
There were also problems with multiple routers on the same network. A Netgear suppled service (forgotten which one) would conflict the same service on another router when attached to the same network. Eventually one of the routers would crash. But first DHCP would stop working. Caused all sorts of problems.
The routers are great but somehow Netgear really screwed up the firmware. It is possible the latest versions are fine, but then so is OpenWRT.
In my experience many problems can be attributed to networking. Most wireless routers have crap support for device discovery. I have some WNDR3700 routers are they were constantly requiring reboots. The only solution was to install a basic OpenWRT firmware - then they were great.
So when a device can not connect to another, or freezes when communicating over the network - check your wireless network. Many problems that are realized on portable devices can actually be tracked back to other devices entirely.