For what it's worth, the libraries that are generally considered "good" (e.g. java.time, Nodatime, Temporal) all offer a "zoned datetime" type which stores an IANA identifier (and maybe an offset, but it's only meant for disambiguation w.r.t. transitions). Postgres already ships tzinfo and works with those identifiers, it just expects you to manage them more manually (e.g. in a separate column or composite type). Also let's not pretend that "timestamp with time zone" isn't a huge misnomer that causes confusion when it refers to a simple instant.

I suspect you might be part of the contingent that considers such a combined type a fundamentally bad idea, however: https://errorprone.info/docs/time#zoned_datetime

> note that all OffsetDateTime instances will have be in UTC (have offset 0)

Is this not effectively an Instant? Are you saying that the instant it represents can be straight up wrong? Or are you saying that because it uses OffsetDateTime, issues are being caused based on people assuming that it represents an input offset (when in reality any such information was lost at input time)?

Also that page implies that they did it that way to align with the JDBC spec, rather than your assertions about misleading documentation.

> POSIX has positive signs west of Greenwich, but many people expect positive signs east of Greenwich. For example, TZ='Etc/GMT+4' uses the abbreviation "-04" and corresponds to 4 hours behind UT (i.e. west of Greenwich) even though many people would expect it to mean 4 hours ahead of UT (i.e. east of Greenwich).

> "Since 2024 the capital ⟨ẞ⟩ is preferred over ⟨SS⟩."

https://en.wikipedia.org/wiki/%C3%9F

Check reference #5 and compare it to the older wording in reference #12.

> "The 55 lessons from Book 1 cover the 1,000 most commonly used characters in the Chinese writing system, plus another 500 included either because they are needed to preserve the logical ordering of the material or because they are especially easy to learn at this early stage."

Those 500 are still from the most common ~3000 total that comprise both books at least, but it means that you really have to learn 1500 characters before you're guaranteed to know the most common 1000. And learn all 3000 before you're guaranteed to know the most common 1500.

I've been going so slowly it's taken me years to reach my current point of character #2170, but eventually I'll get there, even if I've already been reading sentences with characters that I haven't gotten to yet for a while now.

https://www.dreamingspanish.com (or find the Youtube channel)

There's tons of free content to keep you occupied for a while, and then there's a paid tier if you want more down the track. After choosing the level that's suitable, I recommend starting with Pablo's videos - he's the founder and I still like his style the most, particularly his older videos before things expanded. Just click on whatever looks interesting.

If we remove the "sensible" requirement:

    type NonEmptyArray = [any, ...any[]]

I don't think Microsoft are the reason why JS uses UTF-16 strings.