This is a much better article that goes to the usual, high level of detail from a DC Rainmaker post: https://www.dcrainmaker.com/2022/05/shimano-forces-hammerhea...
Expect anything that comes out of his mouth to be colored by his desire to not piss off the gods at Garmin. I've been watching him do that dance for years, refusing to acknowledge major bugs people find in various Garmin products that go unaddressed, to not having a peep to say about the absurd levels of market segmentation Garmin goes to.
Oh hey, here's him not pointing out that the whole thing is Garmin's fault for allowing vendors to utilize private, secret ANT functions. Instead:
> In other words, this is entirely a result of SRAM acquiring Hammerhead earlier this year
No. It's the fault of Garmin for creating "private ANT", mainly because they wanted it for their own purposes. See, Wahoo and others were starting to release competing GPS bike computers (and Hammerhead came along as well)...so private ANT let them lock out other bike computer manufacturers from getting advanced power meter stats, controlling their lights, getting alerts from their radar, etc just long enough to force people to buy their overpriced, under-featured, buggy bike computers.
If anything, if he were in favor of Garmin he wouldn't push this so hard, since it's in favor of Garmin computers that a competitor can't read this data.
https://www.dcrainmaker.com/2019/06/competitor-software-inst...
Garmin and the other manufacturers who control ANT+ created the private channel so that it would be available for experiments when there's no suitable standard profile. There is a standard profile for electronic shifting so you can't blame Garmin if Shimano fails to follow the standard. Garmin does follow the ANT+ profile standards in their power meters, lights, and radars; all of those Garmin sensor devices interoperate correctly with third-party bike computers. The issue described in this post is 100% a Shimano problem and Garmin bears zero blame.