I don't use it myself.
On the page you provided, I see, "not everyone updates their Chrome version immediately, especially updates like this one which require that you restart the browser (and all running browser instances)."
I didn't think that you had a choice, and so, puzzlingly, our fellow user ought to have had Chrome updated to the allegedly safe Flash version.
My thought, if I were Adobe, would be not to allow this before my own release of plug-ins was ready - perhaps a matter of regression testing, that everything else still works - and instead oblige Google to release either Chrome with Flash disabled by default, or Chrome without Flash at all, if their users wanted to install that.
But then, if Google leaves Flash out of Chrome once, they might not want to put it back in again.
I'm assuming that Adobe writes, tests, and bug-fixes Flash, and Google only duct-tapes it into their browser. Like fitted-kitchen equipment that fits inside standard size cabinets, and, of course, is built by a refrigerator company or a washing machine company instead of a kitchen cabinet company.