Supporting extensions, but really now
Friday, October 25 at 09:30–10:20
I have experience with the extensibility of a software being its strength coming from Rails and Ruby. Many language communities have their package managers, plugins, gems, JVM, npm, and architectures these days are typically modular.
All these ecosystems have similar challenges too. Dependencies maintained by the proverbial single individual in Nebraska, lack of documentation, infrequent security patches, malicious actors...
Joining Tembo in July this year, I have ramped up my knowledge of the larger ecosystem, in no small part thanks to David Wheeler's "State of the Postgres Extensions Ecosystem" / "Extension Ecosystem Mini-Summits" work. Now I want to look at Postgres' challenges from that broader perspective again.
Before we can tackle challenges we need to truly understand what's preventing maturity, and we need to measure the work we do to make the stuff we rely on more robust. What would an annual State of the Extensions look like? I have asked different stakeholders and can't wait to share my recommendations.
