lime@feddit.nu 1 week ago
interesting idea. there are already text-based browsers like qutebrowser but they require mastering a command language. creating a natural language interface based on a constrained language is bound to come with the same sort of problem apple had with hypercard: easy to read, diabolic to write. i wonder how they solve for that.
blue_berry@lemmy.world 1 week ago
lime@feddit.nu 1 week ago
there is a rich history of programming languages which are supposed to read like natural language. it gave us beauties like COBOL, SQL, and HyperCard. in other words, it’s not good.
as for text browsers, nyxt is probably the one that’s closest, or some browser mode in emacs.
ultimately what you want with navigation is precision and minimal typing, so a natural language interface is slow, and an ACE interface would be even slower.
blue_berry@lemmy.world 1 week ago
I don’t know. Basically, if you already know what you want, maybe you only want to type down a couple of statements (maybe even from a template or a tutorial that you found online), modify some stuff and then hit enter. And maybe this modifying of language could be the “browsing” part of the browser.
If you look at it like this it would also be immediate and precise. You would only need to add very good code completion tools, e.g. when you click on a noun, you see all the attributes it has in your ontology. Much like in a IDE. There you also “browse” the space of all potential programs with the interface of language with code completion, which act like links in traditional browsers.
lime@feddit.nu 1 week ago
i’m no longer sure if you’re envisioning a web browser or a website builder. your terminology is all over the place.
and no, the semantic web is in no way an an open, global codebase. it’s just a way of structuring html. i know berners-lee wanted the web to be more like what you are describing but the web we have today is not that. you’d need a new protocol.