One month after any given day of the month is, by most people’s intuition, a valid thing to ask for.
Nobody actually thinks this way, when you ask somebody what’s the next month they don’t go, oh today is the x day of the month and I’m going to add days to the current date to see what’s the next month. That’s not how vast majority of people think about this intuitively. Clearly you and people who designed Js Date API do though.
“a month is 31 days in January, and 28 or 29 in February, so adding a month does different things in different months”
That’s how months work. Each month has a different number of days.
If I say to add four days, will it throw an exception if it’s the 31st? No month has 35 days, so I should get an exception, right?
Yeah, it’s how months work.
In fact, this isn’t a hypothetical argument this is how date APIs work in sane languages like Java. For example:
So, you’re talking about throwing exceptions if adding a month yields an invalid date if done without nuance, but then you’re showing an example of just trying to instantiate an invalid date in java.
I believe java has an addMonths method, that in the situation we’re talking about doesn’t throw an exception, but rather limits the output to the 28th/
29th/30th.
Which illustrates my point: intuitive Datetime math involves choosing how you handle edge cases that are routine and not exceptional, like “a month from January 31st”.
The rest of your comment arguing about how people expect months to work just makes me feel like you’ve never actually talked to a business stakeholder about requirements.
If I say to add four days, will it throw an exception if it’s the 31st? No month has 35 days, so I should get an exception, right?
Yeah, it’s how months work.
That’s just insane. An API that doesn’t increment the month when you pass the end while adding days is just broken.
I encourage you to actually try using Java API to see how it works if you don’t think my example is illustrative enough. Meanwhile, the only insane thing here is you thinking that how an API works has anything to do with business stakeholders and requirements. This statement clearly illustrates that you don’t understand how to translate business requirements into code and perhaps should spend some time learning how to do that instead of trolling here.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Nobody actually thinks this way, when you ask somebody what’s the next month they don’t go, oh today is the x day of the month and I’m going to add days to the current date to see what’s the next month. That’s not how vast majority of people think about this intuitively. Clearly you and people who designed Js Date API do though.
That’s how months work. Each month has a different number of days.
Yeah, it’s how months work.
In fact, this isn’t a hypothetical argument this is how date APIs work in sane languages like Java. For example:
The fact that you think what Js API dies is preferable to this is frankly surreal to me.
So, you’re talking about throwing exceptions if adding a month yields an invalid date if done without nuance, but then you’re showing an example of just trying to instantiate an invalid date in java.
I believe java has an
addMonthsmethod, that in the situation we’re talking about doesn’t throw an exception, but rather limits the output to the 28th/ 29th/30th.Which illustrates my point: intuitive Datetime math involves choosing how you handle edge cases that are routine and not exceptional, like “a month from January 31st”.
The rest of your comment arguing about how people expect months to work just makes me feel like you’ve never actually talked to a business stakeholder about requirements.
That’s just insane. An API that doesn’t increment the month when you pass the end while adding days is just broken.
I encourage you to actually try using Java API to see how it works if you don’t think my example is illustrative enough. Meanwhile, the only insane thing here is you thinking that how an API works has anything to do with business stakeholders and requirements. This statement clearly illustrates that you don’t understand how to translate business requirements into code and perhaps should spend some time learning how to do that instead of trolling here.