2 ms·
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 technical
by sgt 2mo ago
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 2mo agoPeople will use it if it really delivers gain and can solve problems PG can't.
- f311a 2mo agoIt takes years to test it thoroughly in real environments. You don't want your data to be silently corrupted.
- insanitybit 2mo agoPeople have rapidly adopted far less tested databases when the dbs have claimed to solve real problems.
- touisteur 2mo agoEspecially if it can be run as a read-only replica.
- yieldcrv 2mo agoTheir 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 2mo agoThat's a pretty gloomy view
- yieldcrv 2mo agoThey 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 2mo agoWhat are we going to do about this?
- yieldcrv 2mo agothis 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
- 59nadir 2mo agoThere's also the fact that it's basically vibecoded.
- whateveracct 2mo agopotemkin industry. jeez.
- quadrifoliate 2mo agoWe 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.
- ozgrakkurt 2mo agoPeople 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.
- NautilusWave 2mo agoThe possibility of competition, and an existing proof of concept, could motivate the Postgres team to pursue performance initiatives that they otherwise wouldn't.
- mindwok 2mo agoI don’t think this is true. There’s plenty of signals for trust - if pgrust keep pouring time, money, and effort into this and get people actually using it even in non critical workloads, it’ll snowball from there. Imagine 2 years from now it’s being used in a couple dozen large companies - people wouldn’t think twice about using it.