This is going to cause trouble with several websites that use "password" inputs for other sensitive data like credit card numbers and SSNs. The discussion mentions that this is a misuse of the password input, but it's a very common misuse of it.
The discussion stresses that Firefox is the third major browser to implement this feature, but what I don't think they understand is that their username/password detection algorithm is the weakest of the three browsers.
If I create a form that contains a dozen fields, one of which is labeled "Owner's Email" (type=text) and another that is labeled "Owner's SSN" (type=password) with several fields in between, Firefox thinks this is a login and prompts the user to save this information. Chrome and IE are smart enough to recognize that just because an email address and password field were somewhere on the same form, that this isn't login information.
We've addressed this issue in the past by turning autocomplete=off for the SSN field, but now we'll have to re-implement input type=password using input type=text with some javascript. Otherwise, our users are going to accidentally click "Yes" at some point when prompted to save their password and have the form auto-filled for each subsequent entry.
While Google's voice recognition is much, much faster, the other comparisons are mostly apples and oranges. As long as you stick to what's in their wheelhouse, both perform fairly well.
Siri is a "personal assistant" while Google Search is more of a "personal librarian."
I don't understand why so many people are taking issue with this and missing the obvious point. You don't need to know what the current date is. It's not asking you to schedule something in the past or in the distant future.
It's showing you the next two occurrences of the time you requested and asking if you want to be notified on the next occurrence of that time or the following one.