Was it just me, or at least on the first page, there wasn't much here of substance? Felt very click-baity. The grain of truth is that of course, complexity req

Was it just me, or at least on the first page, there wasn't much here of substance? Felt very click-baity. The grain of truth is that of course, complexity requirements can be outdated advice given social engineering (particularly password reset) and password reuse. But I would draw a line at not caring how passwords are stored. And ultimately, attackers go for the weakest link they can perceive. The first company to suggest that, like libraries, PIN numbers with default values are good enough, will be the first to have random, brute force attacks against them succeed. Unless you change the game entirely, such as by requiring two-factor authentication, a random password is still required to protect from unauthorized account access and I don't see that advice changing anytime soon. It's even easier now that such random characters can be generated by apps and browsers. Of course, such password stores might in turn be the next targets, but malware has yet to make a large dent in iOS, as far as I can tell. Let's hope we're a long way off from fake cell towers...