My point was just that formal methods can have a tremendous positive impact even if academics are the only ones using them, as long as the output from those efforts do get used. So I'm not sure distinguishing between "using formally verified software" and "using a formal methods tool directly" is a helpful distinction when measuring industrial impact.
Also, formalizing architectural properties for the world's most popular cloud service is probably even rarer a task than formalizing language specifications.
I agree, but I see some chance of TLA+ of getting wide(r) adoption, precisely because it is rather easy to learn and uses math that most engineers are already familiar with. Also, it allows gradual verification: specification -> model-checking -> proof (with each additional step being completely optional)
> not that everyone and his brother can use formal methods for every WordPress website they churn out.
I don't know about WordPress websites, but Amazon engineers do use TLA+ to specify many (most?) AWS services.