"the standard is for devices to generate (multiple) random addresses"
It's still a pre-small LANs approach. As if all devices are simple clients only connecting to external resources carefully managed by dedicated people, and never servers offering services to others. If you have, for example, a NAS, it can't really generate random addresses and change them over time, because how would you be able to access it? Every time check what damned addresses, in hex, it generated?
If you want to access your other PCs, should you look every time at what random addresses they got first? What about my router and access points?
IPv6 wholly underestimated the need to match addresses with a working name resolution mechanism, because you can't really expect people memorize IPv6 addresses, especially when they change.
IPv6 was designed in an era when people where expected to have a single *client*, which just needed an address to make its calls.
But now even in small networks you have many devices, and you need something like DHCP+DNS (or anything equivalent), especially when you use VLANs/subnets and simpler resolution methods for network discovery does not work.
Just, does Android support DHCPv6 now? On the other end, Windows didn't support RDNSS until some recent version of Windows 10. That's because IPv6 instead of being built on clear standards didn't address clear, obvious needs, leaving them to implementations acceptable in 1996 only. And refusing to address them properly and fully later. IMHO SLAAC was a bad idea from the beginning, especially from a management perspective.
Still, you may want some machines to have static addresses to access them even if the name resolution system doesn't work, and thereby you may also want to avoid to make them visible outside.
An IPv6 roll out needs a simple way to manage the network, assign addresses and map them to host names automatically. While systems managed by dedicated and skilled people may have little issues, it could become soon a nightmare for smaller systems which doesn't have the required skills available, unless network devices have the required software to make the configuration, and the transition, easy.