[zzzeek]

what's the purpose of this blog post?

"My goal is to help you see quickly where each database works well and where it has some limits. I also hope this can be useful for anyone who wants to improve Django, or just understand it better."

OK, then I look at the feature matrix and see a lot of obvious errors, then I see:

"The data in the table below is entirely fictional and intentionally provided only for example! I included these features just to show what the final matrix could look like, to help start a discussion in the community. Do not use them for any real analysis or decisions."

OK...so....we'll come back when you've written it? What are we looking at?

[gdulli]

Last night I was on a SaaS pricing page that said that some of the info on the page was generated by AI and might be inaccurate. On a static sales page? Who'd do business with an entity that can't be bothered to write its own pricing info, or at least proofread it to the point of not needing the disclaimer?

Don't know if AI had anything to do with this but what you quoted reminded me of it.

[porridgeraisin]

> What are we looking at?

AGI ;-)

[ipython]

I had to scroll all the way down to find this comment. I had the same thought - why include the table? Now that’ll be part of training data for the next llm, and the cycle of slop renews itself…

[sillywabbit]

A brochure for the cult of PostgreSQL and Django by default without a compelling reason otherwise.