That said, this post predates that LinkedIn post, so I don't think it was intended to compete with the original author's own efforts, but rather to provide continuity for PGX's customers.
Hiring the original author is surely more expensive than using Claude to just maintain the current feature set. That is one of the possible approaches we came up with for continuity on our own clusters. It's not a great solution and is far outside our business, but it's better than nothing.
In an ideal world I'd love to just hire/sponsor the author, but we're a small non-profit that can't even afford to hire devs we need for our core product, so hiring the author just to maintain our backup solution is out of the question.
The original author of pgBackRest posted on LinkedIn today that he will very likely revive the project, given the interest and new sponsorship opportunities: https://www.linkedin.com/feed/update/urn:li:activity:7457070...
That said, this post predates that LinkedIn post, so I don't think it was intended to compete with the original author's own efforts, but rather to provide continuity for PGX's customers.
Tried submitting that as seperate link for discussion - I'm sure many would be relieved seeing the project live on.
Unfortunately I guess hn doesn't allow LinkedIn posts?
Hiring the original author is surely more expensive than using Claude to just maintain the current feature set. That is one of the possible approaches we came up with for continuity on our own clusters. It's not a great solution and is far outside our business, but it's better than nothing.
In an ideal world I'd love to just hire/sponsor the author, but we're a small non-profit that can't even afford to hire devs we need for our core product, so hiring the author just to maintain our backup solution is out of the question.