[suggestion] adoption effort

[hyusetiawan]

may I suggest, as part of the marketing to get this project more adoption, is to add a plugin easy install mechanism for the popular orms out there? like drizzle + prisma or even hook into the graphql community, they are revamping the subscriptions too in the new graphql version. There are ways to get linked-ql to be the defacto realtime capability here

[ox-harris]

LinkedQL definitely intersects with existing tooling. So, yes.

but I guess it's in ways that change the conversation—from "something that composes with today's patterns" to "something that formalizes what those patterns have been approximating from different directions." And I think that's the perspective from which LinkedQL starts to make sense..

This is roughly how I think about the existing model versus what LinkedQL is exploring.

Today:

                ┌──────────────────────────────────────┐
                │ ORM                                  │
Application  ⇄  │ GraphQL / REST                       │  ⇄  Database
                │ Realtime                             │
                │ Sync                                 │
                └──────────────────────────────────────┘

LinkedQL:

                ┌──────────────────────────────────────┐
Application  ⇄  │ db.query(sql, { live: true })        │  ⇄  Database
                └──────────────────────────────────────┘

Concerns like object-relational mapping, realtime, and sync stop being separate infrastructure and become properties of a single thing: the application–database relationship itself.

• the query itself becomes the subscription ({ live: true })
• the query declares the application's object model (SELECT { ... })
• sync emerges from the database itself (CREATE REALTIME VIEW ...)

more like the full application–database contract codified at the query boundary.

Once LinkedQL is understood this way—as not just a retrieval primitive, but as the application–database contract—the integration question changes too.

it stops being "how does LinkedQL plug into existing patterns?" and becomes "which parts of those patterns are now properties of the contract itself?"

I suspect we're describing the same "de facto" destination from different angles. I'm curious what that picture looks like from your perspective.

[hyusetiawan]

it's the same, the fundamental thinking is that, there are a lot of open source projects that you can provide value for and that would increase your adoption. You mentioned graphql, look at pothos community, but honestly if you are able to provide value for the drizzle or prisma communities, that would be amazing