My hope was that the line "It's the only way we can reduce the number of data breaches and crashes" would seem immediately ridiculous to everyone.
Given the history of surprising security bugs in mature code being discovered by a decentralized collection of users and hackers over long periods of time -- a phenomenon we've all witnessed over the years -- I figured the notion that a slow-moving, bureaucratic supreme panel of code judges effectively and decisively removing security problems basically didn't make sense.
I don't know now. Maybe it makes more sense than I thought.
But if you look back at the history of highly-regulated technology industries, every single one started out lightly regulated and free wheeling. Early railroad, automobile, oil drilling, aviation, and telecommunication companies (to name a few) were all full of self-taught innovators who wanted to move fast and disrupt things.
As software eats the world, the world will become less and less tolerant of shitty software. I will not be surprised at all to see demand for credentialling and oversight grow even in the next 10 years.
The programming equivalent would be like forcing coders to demonstrate competency in everything from embedded systems programming to OS development to packaged application to web back-end, to web front-end, mobile apps, algorithms, networking, language design, compiler optimization, etc.
The way it works now, coders can specialize and that makes it easier to self-study. Learning all about web front-end dev is a lot easier then learning about every type of programming there is.
If you want credentialling, it would have to be more like medicine, where people have to pass the boards in their specialty only.