I think everyone understands that the usability isn't optimal. Indeed, in my son's university program, they have a course on UE design, and pgAdmin is used as a case study of a suboptimal user experience (sorry, don't shoot me, I'm just the messenger!)
I've logged several feature requests relating to usability, and would dearly love to see some of them get addressed. But then I look at what's in the release notes, and see that the team is working on really core capabilities. I.e., they have to support everything that PostgreSQL can possibly do, most of what is fixed is way, way beyond my knowledge. As a developer of a web app I just need the most basic features, whereas the pgAdmin team has to collectively understand absolutely *everything* about PostgreSQL. And in my experience as a development manager, the kind of people who tend to like all the nitty gritty details of databases rarely tend to have a passion for UE design--different strengths and skill sets are required. So I'm not surprised that a team that can understand the complexity of something like PostgreSQL doesn't agonize over optimizing the UE.
But of course, anyone who is knowledgeable and passionate about UE design is free to contribute, and perhaps make some improvements. And at that point I look down at my feet awkwardly and mutter something about not having the time to immerse myself in the project, and then come to the happy realization that if it works and is free, then I can live with the usability rough edges.
So... we have a product that has to encompass a mind-boggling range of functionality. Could it have better usability? yes. Can I live with it, as is? yes.
