It seems like a lot of effort is being spent on supporting all of the major 
browsers out there, and working around the quirks that arise from pgAdmin4 
being browser-based. Recognizing, however, that using a browser as he basis for 
screen output achieves a major goal of platform independence, I have to wonder 
if it might make more sense to target someone’s “web view” software (e.g. a 
lightweight browser designed for generating output from a local server/daemon, 
and not loaded down with all the extra “stuff” that comes from hitting any web 
server in the world and trying to be everything to everyone as the major 
browsers do.

One example of the quirks that I refer to are the hoops you (as the software 
developers) and us (as the users) have to go through to get a “standalone” 
desktop version that does a reasonable job “as compared to other desktop 
software” of restoring state when reloaded. All the extra work of configuring 
the local system, etc. would be unnecessary with a dedicated web view. All the 
effort to support all of the major browsers would be unnecessary, etc. 

Are there sound technical reasons why this approach has not been adopted?

Reply via email to