All ports, all protocols Internet browser. Open ports and support protocols to direct browsing of databases, and other internet resources, make web browsers support accessing them directly and nicely.
What people currently think of a browser, is a "Web browser," that works on HTTP(S) and primarily 80/443, that are on top of TCP-IP. The idea of "Internet browser" is that any record in any system could have a "url" to any other record in any other system may be useful in many situations, including the creation of semantic web.
Given a good popular data browser, many would probably care to open their databases for public access with default database ports, like 5432, or 27017, for data consumption, and so, we could start using hyperlinks like:
The database programming languages like (PL/SQL, PSL, etc.) would come back to relevance, allowing the flexibility to define the added business logic and functionality, which these days usually is provided by building an API on to of databases.
Today, while most of the web pages on ports 80/443 are open to public, traditionally, most records in databases are behind an authentication, and thus, people are not inclined to make such links (they are inclined to scrape the web rather than properly use databases).
Given an existence and wide knowledge of a good data browser (with ease of use and powerful analytics capabilities on local computers), it is likely to expect that people would care to make proper public access to them, and create a web of data.
rest:// endpoints, or
graphql:// endpoints, or
ftp:// endpoints, or anything else just as easily as we browse
http://, with nice out-of-the-box UI, right inside the browsers.