The reason the ecosystem maturity is so important for bazel is because its design encourages complete reimplementations. The rust packaging rules for bazel reimplement a subset of cargo's features from scratch. The docker rules reimplement image building from scratch (they don't actually use docker). The (Google maintained) python rules shell out to pip, but it's got a ton of problems, some packages are unbuildable, and it busts the cache constantly and redownloads everything.
If you're using C++ or Java, I can heartily recommend Bazel as an improvement to your current tool. If you're using anything else, hold off until the ecosystem is more mature.
I can believe all of these reimplementations are worth it for hermeticity, but I seriously doubt most shops need the extreme hermeticity Google does. It's a thing that really matters at gargantuan scale.
Good old shortsightedness at play here. No one looks past this year or years to come when faced with changes. Here's what I think, based on history, is happening here:
# Wires are more bad than good for average consumer:
a. Neglected security based on assumption that since it's not wireless, it's immune to eavesdropping (think side-channel attacks). Wireless puts security upfront and center.
b. Cables get lost, break, are not long enough, are not compatible, damage the connectors, bad cables damage the device, cost extra, etc. Wireless doesn't.
c. Cables are cumbersome. They get tangled, you need to remember to carry them, have backups, etc.
d. Cables have short range.
Apple evidently cares quite a bit about user experience. Wires hurt user experience so they want to get rid of them, one by one. You can't push towards superfast, low power and generally more advanced mobile devices and accessories, if the industry has no reason to do so (because everything works and has for the past 50 years).
It's tiring reading every day how someone is upset because their favorite feature is gone because they can't see past their front door.