In any event, I don't think it's going to make any inroads towards fixing bufferbloat for a single user on the same machine, i.e. where multiple applications are creating several seconds of bufferbloat each, the latency sensitive applications (Skype, Google searches, typical web browsing) are still all going to suffer.
I think it's actually not a router issue but an application issue, in the same sense that CPU overusage by one application is an application issue. Applications just need to be better designed to not bloat a user's network.
Hopefully, the next major Apple OS update will include bufferbloat measurements in Activity Monitor, so offending apps can be named and shamed. But even this won't prevent web apps from having massive bufferbloat footprints (for that the browsers will need to share data with Activity Monitor, or highlight this to the user).
After this, I think pressure from users on application developers to reduce bufferbloat footprint and build network efficient apps is the way forward.
Then we will be able to switch to some of the better higher-bandwidth TCP congestion avoidance algorithms without having to settle for algorithms which ignore latency as a congestion signal (packet loss is a poor signal and causes throughput to saw-tooth).