Skip to main content

How critical is it for JSR-310 (new Date and Time API) to be implemented in Java 8?

Very - as JEP 150 states, "the existing Java date and time classes are poor, mutable, and have unpredictable performance"
75% (667 votes)
It would be nice, but we can get by using the current classes
11% (102 votes)
Makes little difference to me
3% (23 votes)
I prefer the current date and time classes
1% (5 votes)
I don't know
3% (28 votes)
Other
7% (66 votes)
Total votes: 891

Comments

Re: How critical is it for JSR-310 (new Date and Time API) ...

I am curious to know if anyone who uses JodaDates has any issues with it. I don't touch a real Java Date until I have to persist, marshall, etc.

Re: How critical is it for JSR-310 (new Date and Time API) ...

This is a must have in any scheduling application, we are forced to use custom libraries

Re: How critical is it for JSR-310 (new Date and Time API) ...

java.util.Date and java.util.Calendar is somewhere between useless and dangerous. A new date API is definately called for. But it's not worth delaying 1.7 for, if it would come to that.

Re: How critical is it for JSR-310 (new Date and Time API) ...

Given the fact that we were expecting this in Java 7, I think it's something that's long overdue and must be included in Java 8.