niklasd

Not that I have any skills in stock-picking whatsoever, but couldn't the recent lukewarm performance not also be an argument for BRK?

I mean their cash pile is also invested in money markets (so you get that), and the rest of the portfolio consists of quality companies where their (combined) valuation didn't explode in the last 1,5 years. So it's an opportunity to invest into something that might not be overheated.

Unfortunately service reliability of Scaleway was terrible last time we used them.

What plan do you have? With gpt-5.5 and the business subscription my 5-hour limit was finished after 10 minutes.

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.

Very fun! If you play it on a big monitor, the games slows down for some reason.

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.

Great, thank you for the reply! The simulation a policy sounds exciting. Looking forward to the news.

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.

(But otherwise I love Supabase! Great job.)

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).

Would that not be a huge security risk? You could access the SSO credentials of your users that way.