Good call. Django's admin site functionality was the killer app for me, so if I'm going to hop off Django to something else then I'm going to want to compare that feature closely.
To each their own but I'm happy for them to pull a premium.
As a customer: They're making gaming on Linux awesome, and my SteamDeck has killed off my console usage (YMMV), I love it so much. I'm way happier to buy games on Steam where it funds cool initiatives like that than on Epic where a big chunk of the value is accrued by TenCent and Disney.
As a game dev Steam also brings a lot of value: A big customer base, to the point where a game with mid-tier popularity can still do brisk business (not nearly as true on Epic). Their backend is unintuitive but has loads more features than EOS. They also offer really cool tech like SDR (Steam Datagram Relay), etc. If you're selling a PC game, there's no better place to be and you get value for the premium.
> I've always wondered why Postgres is so insanely popular.
Just another anecdote: MySQL lost data for me (2004). I spent some time evaluating the projects and Postgres’ development process seemed much more mature — methodical, careful, and focused on correctness. Boring, which I loved.
I didn’t need whatever perf advantage MySQL had so I switched to Postgres and never looked back. And then the Oracle drama and Monty’s behavior around it — not saying he was wrong or right, but it was the opposite of boring — just reinforced my decision.
I like to play with new tech in various spots of the stack, but for filesystems and databases I go boring all the way.
It's a very common misconfiguration, though, because it happens by default when setting up CF. If your customers are, by default, configuring things incorrectly, then it's reasonable to ask if the service should surface the issue more proactively in an attempt to help customers get it right.
As another commenter noted, not even CF's own RSS feed seems to get the content type right. This issue could clearly use some work.