upvote
People will use it if it really delivers gain and can solve problems PG can't.
reply
It takes years to test it thoroughly in real environments. You don't want your data to be silently corrupted.
reply
People are very willing to use new things when something they are using can't do what they want to do.

Dogma is more effective than reliability concerns in my experience. It just happens that the dogma prefers Postgres in this case.

It is just difficult to make these decisions in a more informed way because it requires actual manual testing with the concrete use case and also a decent understanding of databases in question. Chances are you won't have people that understand these things or those people won't have much of a say in decisions.

reply
There's also the fact that it's basically vibecoded.
reply
potemkin industry. jeez.
reply
We still have companies that use COBOL and mainframes due to their longevity and continuity. There is no reason Postgres and pgrust cannot both flourish. I can pick and choose which one to use according to its use case.
reply
Their ai agents will if we keep writing about it

Project managers and Human Resources rolling out overengineered projects will outnumber current software engineers 10 to 1

reply
That's a pretty gloomy view
reply
They will be software engineers or the people doing the software work

And different people will be doing product management and HR

all because today’s software engineers don’t want to babysit AI agents and choose antiquated libraries so that their resume said they'd been using a popular framework for a couple years

Nobody else is playing that outdated game, its just a rotation

reply
What are we going to do about this?
reply
this thread is talking about using a 300x faster library and theorizing a resistance to devs using it

just use the faster library? leverage compute resources more effectively and justify value to an organization better than the next person

otherwise, what needs to be done? I don’t see a problem with any of this aside from organizations risking less experienced people doing less efficient things in other parts of the stack

reply