To me it seems this way; there are pros and cons to unionizing - while there hasn't been a formal discussion, obviously, developers have seemed to have selected for "no unionizing".
I recall there being a call for a union and efforts toward this back in 1998 or thereabouts; 20 years ago roughly. It died out rather rapidly. Maybe related to the dot-com implosion, I don't know.
But...something is going to need to be done. We are rapidly either heading toward needing a union, or we'll be forced to be certified and/or licensed, much in the same way actual engineers are. Maybe a combo of those things.
We are seeing software being integrated more and more into devices and machines that can and do put people into life threatening situations. Self-driving vehicles, drive-by-wire controls, and other things - while none not actually "new" - have been failing in ways that are much more public than in the past, and has caused discussion on the idea of "who is at fault".
Companies are ultimately going to want to shift the burden from them, to their employees. I'm honestly surprised it's taken this long - and the fact that it still hasn't occurred ; I'm not sure why that is.