3 ms·
Yes, this is the exact fix the article suggests making. And then goes on to say that he never did it because it was too hard to format dates in Java or some suc
by NelsonMinar 8y ago
Yes, this is the exact fix the article suggests making. And then goes on to say that he never did it because it was too hard to format dates in Java or some such nonsense.
- SilasX 8y agoIn fairness, it's a bad UX that forces you to change your own workflow to keep it from introducing undesired behavior.
- mywittyname 8y agoIt's bad UX to have messages that are entirely identical from a user perspective, but perform different functions. The email with the functionality to reset your password was no different than the past ones that have no effect. The emails should have specified the expiration date in the text of the email document from day one.
- user5994461 8y ago>>> The emails should have specified the expiration date in the text of the email document from day one. That doesn't avoid the issue. Similar emails are collapsed, it's not about being identical. For example, two orders listing the (different) products you bought might get collapsed, despite being fairly different.
- notJim 8y agoTo be fair, the built-in java date libraries were notoriously difficult to work with until recently.
- user5994461 8y agoAnd don't forget about internationalization. There are more than one hundred languages to support!