Personally not for me. These are very productive once you learn the shape they expect.
But the wheel needs to be reinvented on how to do everything.
I ran have straight forward verbose code with no hidden control flow
pyrolistical
To be honest, the use of AI in your marketing doesn't bother me. But paired with the fact that you have a newish HN account with no comments ever, and no comments on your own "Show HN" in response to others, doesn't put off strong trust signals.
bdcravens
The pronunciation of "Vercel" near the end of the "Typebase in 100s" video was VER-cel, with the emphasis on the first syllable, instead of ver-CEL with the emphasis on the second syllable.
Was the video generated by AI?
stack_framer
I have deployed and maintained plenty of diff setups on GCP, AWS, colo, and I have also used AI for coding, my concern is do we really trust AI to do prod deploy and maintenance of the backend yet? Not to mention what are the limitations here, someone already mentioned queues? But for a straightforward site with limited complexities, it might be cool to try out.
brianpg
I love the (well-disclosed) fake testimonials. Hilarious!
phren0logy
Scratching my head a little bit here, I'm not sure how this differs from NextJS (or Vite) with a layer of drizzle & better-auth.
Not that that layer isn't important. We ended up building something like this at Ingram, nextkit: https://github.com/ingram-technologies/nextkit - but we distribute it as a set of micro libraries that work well together rather than a unified framework. (Auth is nk-auth, built on top of betterauth, and sql is nk-db, built on top of drizzle)
You got to pretty much the same conclusions we did though regarding the "why".
scrollaway
I’ve been curious about trying the Supabase type of RLS model for an app but haven’t yet. I like the idea of the db defined api like postgraphile and hasura but had trouble with testing and ergonomics. This looks pretty nice though, it’s cool that you’re thinking about ergonomics for working with coding agents. I feel like a hard thing with that rn is that everyone is kind of figuring out different workflows for AI coding right now so it’s hard to optimize DX. Can you talk a little about your personal agent workflow and how this fits it?
rgbrgb
Sounds very interesting. I have to agree I didn't like RLS as well. I mean, it's useful but it seems too many knobs to turn...
ishbrzero
I was about the ask a question but you just answered how it is built. I guess I will try it out, it sounds really good.
I love your approach, fake testemonials and all.
desireco42
Fake reviews are a hard no-no imo. Really weird addition, but I suppose it wasn't you who got the idea.
Looks an awful lot like a orpc, just built on top of drizzle instead of raw queries. I'm sure some people want this, but it seems like gross duct tape that will bite you in three years
comments (10)
Personally not for me. These are very productive once you learn the shape they expect.
But the wheel needs to be reinvented on how to do everything.
I ran have straight forward verbose code with no hidden control flow
pyrolistical
bdcravens
Was the video generated by AI?
stack_framer
brianpg
phren0logy
Not that that layer isn't important. We ended up building something like this at Ingram, nextkit: https://github.com/ingram-technologies/nextkit - but we distribute it as a set of micro libraries that work well together rather than a unified framework. (Auth is nk-auth, built on top of betterauth, and sql is nk-db, built on top of drizzle)
You got to pretty much the same conclusions we did though regarding the "why".
scrollaway
rgbrgb
ishbrzero
I love your approach, fake testemonials and all.
desireco42
Looks an awful lot like a orpc, just built on top of drizzle instead of raw queries. I'm sure some people want this, but it seems like gross duct tape that will bite you in three years
ramon156