Such a missed opportunity to call it "Lambo"

then we'd have to ship with a PHP driver from day1.

I sell a middleware I built to access data in Airtable / Google Spreadsheets using GraphQL: https://www.baseql.com

This sure seems very interesting. Have you written the GraphQL layer by hand? Have you tried https://github.com/tailcallhq/tailcall

With tailcall, you can quickly bootstrap a GraphQL service on top of existing APIs. I would love to collaborate on this and help you on board.

This looks very interesting. Would you be interested in adding Retable.io support as well?

Had a similar scrapped idea a few years ago: https://benoror.github.io/laystack-landing/

Provide an API with https://www.baseql.com/

How is this fundamentally different from how something like Sidekiq instantiates a Rails codebase to run background jobs?

More on this: https://news.ycombinator.com/item?id=38531759

Checkout baseql.com to generate a GraphQL endpoint from Google Sheets

Kudos! Sounds like a novel concept for newer trends gravitating back again towards SSR at "The Edge"©

I remember using typicode/lowdb in a past life and wondering why it had to have an ad-hoc ORM-like API when good ol' data structures would do just fine?

Nothing against Svelte (actually the opposite), but maybe showcasing a simplified code snippet in the landing page and make it more framework-agnostic might draw more brains

On the other hand, there might be a chance to showcase specific examples of more trending SSR frameworks such as Remix and Next.js. As far as I can tell direct DB access might make more sense on the server-side (LoaderFunction & getServerSideProps respectively)

Great craft!

Thanks Ben. I appreciate the feedback, I will add vanilla samples but also samples for each framework, including SSR.

The DB access works fine on both places, I use it from svelte kit load function without problems. I haven't played with authenticated SSR, I'll make sure to include that in the samples.

IMO there's no way around building real production apps starting from the UI. Design has to begin with data model. It's like building a House not from the foundations but from the facade.

Agreed. Design needs to be driven by the data model, and the data model needs to be driven by business entities. Any top-down approach is nonsensical, exactly as you describe.

Totally agree with this!

FB should probably make it easier to identify and unsubscribe from those feedback loop silos