• Welcome! The TrekBBS is the number one place to chat about Star Trek with like-minded fans.
    If you are not already a member then please register an account and join in the discussion!

Spoilers Star Trek: Strange New Worlds 1x04 - "Memento Mori"

Hit it!


  • Total voters
    219
Our Saddle Up! review is out!

su-005-th-wide.jpg
 
what you propose is in fact the ISO 8601 standard. I wish it was used by more people.
ISO 8601 has been around since 1988, yet the world hasn't fully converged on it for Calender Date representation on a global level.
The populace is still using the local representation that is common to them.

The major difference between ISO 8601 and my version is that they recommend using only "-" as seperators.

I recommend using "/" & "-" as seperators for easier readability.
I recommend (YYYY/MM-DD DotW) as the standard.
2228/12-08
 
It's so great you have to buy a PDF to understand it's use.

I prefer DD-MM-YYYY.
I think the international format of YYYY-MM-DD is just more useful, because it can be naturally sorted, and more readable, in addition to going from more general to more precise, which is logical. Japan uses YYYY.MM.DD, which is just as good.
 
It's so great you have to buy a PDF to understand it's use.

I prefer DD-MM-YYYY.
I didn’t buy any PDF and the use is quite intuitive. Also it’s great to keep your folders and files ordered.

The system you mention has none of the advantage of YYYY-MM-DD, but at least it makes sense. The one with the day in the middle should be punishable with death.
 
I think the international format of YYYY-MM-DD is just more useful, because it can be naturally sorted, and more readable, in addition to going from more general to more precise, which is logical. Japan uses YYYY.MM.DD, which is just as good.
I'm trying but I cannot stand leading year. In my daily use it feels inordinately clumsy and unreadable.
I didn’t buy any PDF and the use is quite intuitive. Also it’s great to keep your folders and files ordered.

The system you mention has none of the advantage of YYYY-MM-DD, but at least it makes sense. The one with the day in the middle should be punishable with death.
I expect my executioner shall be arriving shortly then?
 
I'm trying but I cannot stand leading year. In my daily use it feels inordinately clumsy and unreadable.
I suppose it takes some getting used to. It's not ordered how one pronounces it, either in French or English, but it makes logical and mathematical sense. And that, of course, appeals to me.
 
I suppose it takes some getting used to. It's not ordered how one pronounces it, either in French or English, but it makes logical and mathematical sense. And that, of course, appeals to me.
Ah. Math never appeals to me. I can appreciate the logic, but in my day to day work there is not a single aspect that appeals to me in conversation. Which, is how my life is run is with interacting with people.
 
I know. Requirements might be different, though, or perhaps she just felt more inspired on the other show.

I recently watched her in a video interview. She mentioned the style of the edit (not getting in the way of the editor) and making changes after spotting sessions with the director. She talked a lot more about Michael Giacchino than Jeff Russo when they both were brought up in the conversation.

Maybe that's where some of the differences lie.
 
Slashes create difficulty in current programming language.
And file systems. “/“, “\” and “:” are special characters and are better avoided to name files, as different OSes might interpret their presence differently and incur in issues.
For example, applications that have a classic Mac OS legacy allows for “/“ but not for “:”, as that used to be the path separator, while for those coming from a unix background (most of them these days) the opposite is true. The result for this is that “:” will become “/“ and viceversa in file names depending on the app you use, even on the same system.


I expect my executioner shall be arriving shortly then?
no later than 2022-06-03.

I'm trying but I cannot stand leading year. In my daily use it feels inordinately clumsy and unreadable
this is not meant to be used in conversation, it’s mainly for when you want to be very clear to avoid confusion or when you’re dealing with a huge amount of dates, especially for archival needs.
I’ve been using this system for tracking my gigs over the years, for example, and before that I used it for versioning during my programming days. If I need to meet a friend on Friday I’ll just tell them “let’s meet on Friday”.
 
ISO 8601 has been around since 1988, yet the world hasn't fully converged on it for Calender Date representation on a global level.
The populace is still using the local representation that is common to them.

The major difference between ISO 8601 and my version is that they recommend using only "-" as seperators.

I recommend using "/" & "-" as seperators for easier readability.
I recommend (YYYY/MM-DD DotW) as the standard.
2228/12-08

ISO 9001 certification didn't prepare me for ISO 8601.
 
this is not meant to be used in conversation, it’s mainly for when you want to be very clear to avoid confusion or when you’re dealing with a huge amount of dates, especially for archival needs.
I’ve been using this system for tracking my gigs over the years, for example, and before that I used it for versioning during my programming days. If I need to meet a friend on Friday I’ll just tell them “let’s meet on Friday”.
Ah, well, I still don't even with my archives. It looks very clunky.

no later than 2022-06-03.
Better hurry.
 
If you are not already a member then please register an account and join in the discussion!

Sign up / Register


Back
Top