Just burned through my 5 hour window in Codex (Business plan) in 10 minutes with GPT-5.5. Was excited to use it, but I guess I have to wait 5 hours now (it's not yet available in the API, so I can't switch there).
We also experienced hitting our Claude limits much earlier than before during the last two weeks. Up to a degree where we were thinking it must be a bug.
I found his take on the space data center a bit negative. No idea if it is feasible right now, but you could have made the same jokes and ridicule about the feasibility of electric cars (batteries too weak!) before Elon build Tesla.
And Patrick just lists some reasons why it is currently hard to do. I'm by no means a Elon fan, but if anyone could pull it of it's him, and attempting these hard challenges is a good thing.
I tried it out and it worked really well for us – awesome tool! The spec-driven approach is a bit different then the usual back-and-forth with agents, and if you invest properly in writing specs it pays of.
From an investors point it's very unattractive to invest in a early-stage startup where half of the shares are in the hands of a person not working there anymore.
About the "as complex as you need": RLS can get slow very quickly for aggregate queries, and is hard to debug (since query planner doesn't work smoothly with RLS).
We have a dashboard that displays aggregated stats for our admin users, and we hit serious performance issues with ~600 users with our first implementation. This repo helped us: https://github.com/GaryAustin1/RLS-Performance
Some additional feedback: In my opinion testing RLS is a problem.
Additionally, I find it hard to keep a good overview over the rules. E.g., in a multi-tenant application one needs to secure every table with a restrictive rule, and it's easy to make a rule permissive, since that is the default & it's not indicated in the Studio UI.
When generating migrations with 'supabase db diff' views are being recreated without 'WITH (security_invoker)' even though they had security_invoker turned on before, leaving your database exposed. Easy to miss, even when you're aware of that.
RLS is just so full of footguns that I find it hard to justify using it in a production system.
Great news! Question to the Supabase team: How does Login with Azure (Social login) and SSO (Azure) differ? From my superficial understanding, implementing Login with Azure is enough for logging-in users with Azure AD accounts (and linking their accounts to existing ones).
Actually, that is perfectly normal in many tax systems, e.g. in Germany. Afaik the tax law doesn't care where the money comes from – it could be from a completely illegal activity, and you still own taxes on gains.
The last point always confuses me. Twitter can show ads to me without me having an account. Instead, they block me from reading on Twitter after a few tweets, thus loosing my eyeballs. Maybe that's compensated by signups, but it certainly didn't work for me.