[laminarflow027]

Hi, I work at Kuzu and can offer my thoughts on this.

You're making a fair observation here and it's true for any high level query language - SQL and Cypher and interchangeable unless the queries are recursive, in which case Cypher's graph syntax (e.g., the Kleene star * or shortest paths) has several advantages. One could make the argument that Cypher is easier for LLMs to generate because the joins are less verbose (you simply express the join as a query pattern). This post is not necessarily about graph analytics. It's about demonstrating that it's very simple to develop a relatively complex application using LLMs and a database fully in-browser, which can potentially open up new use cases. I'm sure many people will come up with other creative ways putting these fully in-browser technologies, both graph-specific, and not, e.g., using vector search-based retrieval. In fact, there are already some of our users doing this right now.

[echelon]

This is really cool, but I'm super anxious about entering my personal data, especially LinkedIn connections.

Is there some other demo you could do with public graph data? It'd be just as cool of a demo, but with less fear of information misuse.

I'm even more anxious about leaking information about my professional connections as I am leaking my own data.

[laminarflow027]

Your concern makes sense, but in the demo we show, all your private data AND the graph database AND the LLM (basically, everything) is confined to your client session in the browser, and no data actually ever leaves your machine. That's the whole point of Wasm!

The graph that you build is more for your own exploration and not for sharing with the outside world.