The release of SDKs, and softdevices, and silicon are accelerating. If you are supporting customers on SDK12, who have heard about the shiny new features of SDK14, by the time you've signed the contract to do the migration, Nordic is imminently releasing SDK16. Forget the odd numbers in between.
Our solution was to standardize all of our conversations, by first saying, 52-132v3-12 has this bug, yadda, yadda. And that worked great for a couple of months, until Nordic decided to release a better product, the nrf52840, but couldn't find enough courage to make a unique name for it.
So, I predict that in the very near future, Universities everywhere will make Linear Algebra and Deep Learning prerequisites for Introduction to C and Embedded. Because thats the only way you'll ever stay ahead of anything for more than an instruction cycle.
I haven't used ANT in a project yet, but I've worked at places that have, just on other teams. It has a more restrictive license, and you have to sign NDAs to even get the key binaries. Thats not to say that Nordic's mainline BLE is open source, but the closed source binaries are freely distributed.
My educated guess though is that Bluetooth developers have "tricked themselves" into thinking they've mastered a design, when they've actually just learned a little more about todays implementation. But as any nordic developer knows, focusing for any measureable amount of time on SDK12 just means you're gonna be super pissed when you hear about SDK13, and thats because nRF decided to totally rewrite SDK14, which will eventually fail hard enough long enough to convince them to spin up into SDK15.
But like they always say, Trust us, we only hire the best.
Edit: something something word word