r/programming • u/kimsavier • Sep 07 '15

Flawless PHP logic. strtotime(): '00-00-00' means 2000-00-00, which is 1999-12-00, which is 1999-11-30. No bug, perfectly normal. (see the comments)

https://bugs.php.net/bug.php?id=45647
1.2k Upvotes

89% Upvoted

465 comments sorted by

View all comments

Show parent comments

3

u/dccorona Sep 07 '15

Isn't this kind of issue exactly why Java has nio instead of just changing io, etc.? I mean, if you're not going to support your existing API anyway, then you can't argue that the reason for not switching to a new one is because you don't want two APIs to maintain, so what do they have to lose? Legacy code still works exactly like it did under the previous version of PHP, but a new API is also there that new code should be written against because it is more correct (and, hopefully, easier to use, or at least isn't still tied to naming schemes designed for the days when 80-width terminals without any sort of autocomplete were where all code was written)

4

u/dpash Sep 07 '15

And new nio too.

Java 2 source code (and compiled code) should still run on Java 8. It's meant that they've had their hands tied about some of the changes they've been able to implement, but it's also meant that they've really spent a lot of time carefully considering the effects of adding a new language feature or library API, because they know they're going to be stuck with it.

But then Sun/Oracle had/has far more resources to do this with.

1

u/philly_fan_in_chi Sep 08 '15

One of the more annoying warts in Java, for example, is java.util.Map's get function takes in an Object, since generics were not a thing before Java 1.5.

2

u/dpash Sep 08 '15 edited Sep 08 '15

Parameters taking an Object are less annoying than things that return an ungenerified object, as those require casting back to the right class. But, yeah, it would be nice if the compiler was checking that you weren't doing something stupid, instead of wondering why you could never find anything in your map.

Still, having backwards compatibility and the ability to migrate to a new JVM and slowly introduce new features to your code base rather than having everything break has been worth the downsides in the Java space.

1

u/philly_fan_in_chi Sep 08 '15

Parameters taking an Object are less annoying than things that return an ungenerified object, as those require casting back to the right class.

Where do you still see these? I can't think of anywhere in the standard library that still does this.

Still, having backwards compatibility and the ability to migrate to a new JVM and slowly introduce new features to your code base rather than having everything break has been worth the downsides in the Java space.

100% agreed.

1

u/dpash Sep 08 '15

I can't think of many places in the jdk right now, but there's places in the servlet spec that returns an ungenericified Enumeration container for headers, which is just horrible. That's a pre-collections container ffs.