- ISO 8601 is paywalled
- RFC allows a space instead of a T (e.g. 2020-12-09 16:09:…) which is nicer to read.
RFC2795, because the IETF guys work hard, and then play hard on April fools.
Yeah I like a girl who is firm on her choice of date time format…😂😂😂😂
I personally have a list of 14 RFCs I won’t compromise on when it’s a first date
A space is more problematic than a T tho
Skill issue
For a skilled pro like you I suggest using epoch time for everything
Its funny because everything about ISO 8601 is covered on its Wikipedia article. Very few people need to spend the francs to need the spec.
If you want to be compliant for a standard you need to have a copy of it. Luckily it’s only companies that really need to buy them
You HAVE to read the spec if you want to be compliant, you can’t just hope every detail is on wikipedia
You’ve just become the nemesis of the entire unix-like userbase for praising the space.
What’s the issue with the space?
Top post of the hour is about an RFC from >20 years ago.
This is worse than the Linux stuff.
Y’all a bunch of nerds
You’re not wrong
Room for one more
Being a nerd is fun.
I’m a Linux nerd and even I don’t get this 😭
Relevant XKCD: https://xkcd.com/1179/
Counterargument: https://xkcd.com/927/
allows a space instead of a T
That’s a bug not a feature
It’s really a skill issue if replacing
Tby[]in your regexp is hardThis is the most junior developer comment I’ve seen in a while.
Nobody that’s competent thinks that’s shit is hard. That’s not the point.
The point is, it makes it easy to make mistakes. Somebody might see all of one type of strings, assume that’s the format, and forget to enclose the thing in quotes, causing mysterious bugs years later when a differently created date filters into the system. You might have a regex error, you might split incorrectly, you might make a query that works the wrong way and gives an incorrect aggregate, and none of that is due to lack of skill. It’s due to not knowing it’s the rfc standard, not the iso. It could be due to not even realizing the rfc allows for that or is different.
Software engineering in practice is not about making sure there is at least some way for people to use your library/standard/pattern. It’s about making sure the way to do it that’s most intuitive/obvious is also foolproof, easy, and efficient. Adding the space makes debugging harder and adds footguns which is exactly what good software engineers want to stay away from. Otherwise we’d all be writing in assembly. But since you aren’t, maybe you are the one with a skill issue. Either that or you really misunderstand this field.
allows, not requires. It basically means you can use space instead of T when showing it to end users and any technical person can just use T
Development wise, It’d be better if it’s required not allowed. Best case scenario, it’s just another redundant if statement.
The amount of things allowed by ISO 8601 is even more than what’s allowed by RFC 3339, if you take the time to look at https://ijmacd.github.io/rfc3339-iso8601/
iSO
Well, they cover very different formats: https://pbs.twimg.com/media/FdzPYu-UAAADHEq.jpg
I don’t even know what ISO 8601 is, but I agree with the sentiment
I don’t get this one.
https://programming.dev/c/programmer_humor is leaking.
They’re both standard for the format of dates and times, like
2023-12-13 15:52:21. I guess one of them isn’t free, though? TIL.
