Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That javascript chose to offset from 1900 was simply because every system back then used to, including Java.

Once that had been done, future versions of javascript had to maintain the same behaviour. This is where I'm using the backwards compatibility argument.



Seems like JS could have called it `getYearOffset1900`, or `getYearOffet`, etc, rather than `getYear`.


Agreed. What I've read is that they basically duplicated the Java API, which had getYear()

I suppose the offset method was really quite entrenched so no one thought to special case that function, instead special casing the "2025" returning getFullYear()




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: