The technical brief also states that:
The Thunderbolt protocol physical layer is responsible for link maintenance including hot-plug detection, and data encoding to provide highly efficient data transfer.
A novel time synchronization protocol that allows all the Thunderbolt products connected in a domain to synchronize their time within 8ns of each other.
And by leveraging the inherently tight timing synchronization (within 8ns across 7 hops downstream from a host) and low latencies of Thunderbolt technology, broadcast-quality media can be produced using Thunderbolt products.
That doesn' t mean developers have nothing to do, but I think that Intel has done its job. Just as with every technology, the implementation also needs to be done properly.
First, hot-plug detection of the Thunderbolt connections does not imply proper hot-plug operation of the PCIe devices downstream - that's up to the 3rd party device drivers for those devices.
Second, having time synchronization of 8 nsec does not mean that you have latencies of 8 nsec.
In fact, it's bloody impossible to have latencies that low. Seven hops with 1m cables would have one-way latencies of at least 23 nsec - simply based on the speed of light. Look up "Grace Hopper nanosecond"....
You may be optimistic. I've developed and supported device drivers, so I have a more cautious view about what can happen when the bus latencies and timings change radically.
Couple that with the fact that very few 3rd party devices drivers have been developed for Apple OSX, and Margo Channing's famous misquote comes to mind:
"Fasten your seat belts, it's going to be a bumpy ride."