[
https://issues.apache.org/jira/browse/LANG-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926623#comment-17926623
]
Elliotte Rusty Harold commented on LANG-1763:
---------------------------------------------
Even if someone appeared tomorrow ready to contribute such a wrapper, we still
wouldn't want to maintain it. FastDateFormat is not a class we'd write or
accept in 2025. It made sense when it was added to commons-lang, but its time
has passed. This is exactly the situation deprecation is meant for.
> Deprecate FastDateFormat
> ------------------------
>
> Key: LANG-1763
> URL: https://issues.apache.org/jira/browse/LANG-1763
> Project: Commons Lang
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Priority: Major
>
> FastDateFormat has bugs, is out of date, and solves a problem that no longer
> exists. That is, it's a thread-safe replacement for SimpleDateFormat. But
> SimpleDateFormat should be replaced by java.time classes in Java 1.8 and
> later, which are thread safe. So deprecate FastDateFormat with a suggestion
> that devs use java.time instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
