There is official Oracle documentation saying that we should not use java.util.Date in a new project

I am writing a new Java 8 project in a company. I suggested using the Java 8 API with a date, but one of my staff says the new time-based API is slow.

It's true? I also want to get official documentation from Oracle that will mention what you should not use java.util.Datein new projects.

+4
source share
3 answers

When it java.time.*was developed, this phrase was what I wanted to add to java.util.Date:

"This class is now effectively deprecated by the Time Framework for Java."

, . .

Oracle, java.util.Date. , Instant java.time.* java.util.Date.

+11

Oracle

- , java.util.Date , Oracle java.time ( , , ).

+5

Oracle

Oracle

Oracle Tutorials - , java.time.

'legacy

, legacy.

, - .

, . , , java.util.Date java.time.Instant. java.time , , , .

java.time , , .

, , . : " ".

+3

Source: https://habr.com/ru/post/1681185/


All Articles