On a tangent note it’s amazing how hard it is to have a good case-insensitive search in Postgres.
In SQL Server you just use case-insensitive collation (which is a default) and add an index (it’s the only one non-clustered) and call it a day.
In postgres you need to go above and beyond just for that. It’s like postgres guys were “nah dog, everybody just uses lowercase; you don’t need to worry of people writing john doe as John Doe)”.
And don’t get me started with storing datetime with timezone (e.g “4/2/2007 7:23:57 PM -07:00“). In sql server you have datetimeoffset; in Postgres you fuck off :-)
> And don’t get me started with storing datetime with timezone (e.g “4/2/2007 7:23:57 PM -07:00“). In sql server you have datetimeoffset; in Postgres you fuck off :-)
`TIMESTAMPTZ` / `TIMESTAMP WITH TIME ZONE` exists?
It’s good for ids where you would like complete match (username, localeId, etc.) but not really for stuff like lastname where you would like to support at least most common prefix search as well
Here's one possibility: Anthropic understands the value of the brand and the harness and that those two things are connected, specifically because they came from behind. OpenAI almost accidentally launched a global brand overnight. ChatGPT went from nothing to the kind of english word you hear in non-anglophone countries in about a month. Millions and millions have used it (at least once) and more people associate it with AI than use it. OpenAI's problem is managing the big industry links so that by the time the hype cools down, they're already plugged into tools. Their "moat" is that number of companies that matter is actually small and all those companies like predictable, enterprise shaped solutions with contracts and stuff. Unlike developers who might switch their subscriptions quickly and absorb the productivity cost of switching (or minimize that cost), these big companies don't want to be constantly optimizing compute vs rental rate. They want to convert an unruly value (programmer productivity) to something easy, not replace it with a scheduling or optimization problem.
That was working ok until Claude, specifically Claude Code showed up. This was a really useful code-writing harness (that also signed your commits, advertising itself to everyone) that took what are essentially very similar models and made Opus feel like the future of software while GPT 5.2 and friends are just code agents. The performance, ability to handle long term tasks, all of that was basically similar but the harness oriented the model to reason, shell out sub-agents, write scratch code, add console logs, all the sorts of things that 1. seem like science fiction, and 2. improve output a little. Then from fall of last year to no you don't have developers saying "look what I made with LLMs" or "Look what I made with AI" but "Look what I did with Claude". There are not very many blog posts out there about the future of software being re-written due to GPT 5.2 getting autocompaction, but that same feature spawned thousands of "oh shit!" posts in Claude.
That's not a more defensible moat than name recognition + small N for customers. It's a scarier position because if someone else figures out how to deliver the same result (Opus + sonnet + Haiku in a managed ensemble) in a way that was sharp and viral, the same thing they did to OpenAI could happen to them. They still supply the compute but the fact that anyone gives a shit about them is their harness makes it look like more and better code is being written. If that's your situation, you gently write the OpenClaw guy, you threaten to cut off and sue OpenCode for using subscription sign-in. You don't do those things because of a numerator/denominator problem with token cost and monthly fees. You do it because someone using your models in a better harness is a clear brand threat.
I enjoyed both versions, though the ending in v1 is somewhat crumpled
reply