Shorn

Any regrets about the namespacing or things you’d do differently with it now looking back?

> Less than an hour of my attention.

There's your answer right there, no need to ask.

Without human advice and a metric shit-tonne of guidance (either pre or post) - anything that requires active consideration of future maintenance burden will cost you 2x-10x of the time you think "saved" over a medium-term time-frame.

The alternative is to spend at least 50% (or sometimes up to %100) of the "saved" time in active review and iterative improvement of the solution design.

No RSS feed for their blog.

Holy shit, did you just try to spin serfdom??

Yeah, no corporate bias here whatsoever

> You could make a similar point by saying something like "I don't like the message he's sending so I won't participate"

Sooo.... "be more professional in your writing"?

Why does this person owe you "professional writing" on their personal comment?

Title is not my fault, content:

The version of postgres you think you're specifying isn't exactly the community postgres, it's an AWS maintained fork and this is an example of where they were seeing an error message from a future version of postgres that had been back-ported in the fork (or maybe AWS contributed to PG and it landed in a later version).

---

I guess I knew this - it's obviously not the exact same version, when you stop to think about it (pretty sure the doco tells you this explicitly too).

But I've never personally observed a difference, so I never really gave it a thought.

they will soon

Come to BitBucket. Which is also down. Because they're in the process of failing to roll out an AI feature no one wants [1]. :/

[1] - I say this as a daily user of claude-code, paying $200USD/mth, of my own money, BTW.

The worst kind

This.

If you're building a brand new, multi-language, multi-platform system that uses advanced open-api features - you will get bitten by lack of support in 3.1 versions of tooling for features that already existed and work fine right now in 3.0 tool versions. Especially if you're using a schema-first workflow (which you should be). For example, $ref's to files across windows/linux/macos across multiple different language tools - java, .net, typescript, etc.

If you need (or just want) maximum compatibility across tools, platforms and languages - open-api 3.1 is still not viable, and isn't looking like it will be anytime soon.