Cool project but .. reality is that people will generally not choose pgrust over Postgres, even 5-10 years from now. The problem is not that it may be technically superior and faster by then, it's that it's not built by the trusted Postgres team. There's a lot more to trust than development velocity or performance. It's also about the longevity and continuity of a critical piece of technology.

▲

andriy_koval 2 hours ago | parent | next [-]

People will use it if it really delivers gain and can solve problems PG can't.

▲

yieldcrv 2 hours ago | parent | prev [-]

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

▲

sgt an hour ago | parent [-]

That's a pretty gloomy view

▲

yieldcrv an hour ago | parent [-]

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

▲

sgt an hour ago | parent [-]

What are we going to do about this?

	▲	yieldcrv 33 minutes ago \| parent [-]
		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