21–27 of 27 posts
It’s like next.js but for backend. 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
I’ve been saying for years we need CCR (Client Centric Rendering). What we do is have the server just serve the page and let the client handle most of the rendering. It’s novel and innovative
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 c…
I've only had experience in one full-stack project with supabase RLS so experience is limited. However it seemed like a mess. Seems much more human-maintainable to have a classic spring/golang backend. For sure in some projects, esp mobile apps, it makes more sense, and fable-level models might also keep it from being full spaghetti. Also Supabase at that time wasn't reliable and it's not really made for self-hosting…
Was the video generated by AI?
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?
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?