Refreshing to see this be the top comment, thank you. I agree.
To answer your question, Grok 4.5 seems to be pretty good at simple tasks and gets even some of the trickier ones correct but it tends to struggle with bigger codebases that aren't very uniform. I've noticed that it uses a fraction of the tokens to get to solutions which is really impressive compared to GLM 5.2 which tends to be an overthinker.
I'm not sure if Grok 4.5 will become part of my stack yet but I am genuinely impressed with what it's been able to achieve.
I'm also unsure if Grok 4.5 is the same base as Grok 4.3. Maybe it is and the data they've used in pretraining is additive (the Cursor data) but it feels like a completely different model than the previous Grok versions.
I've come to this conclusion too. It's a bit disappointing. I fully realize this is more than likely just user error. And now with AI agents the maintenance of a Postgres instance is likely less of a burden. But I can't help but yearn for the simplicity of a single SQLite file and bespoke solutions for things like queues, pub/sub, caching, etc.
I think sleep apnea would have killed me had I not gotten the sleep study. I was having 100+ events in the span of a few hours. Anyhow, I use the CPAP everyday. I don't snore anymore and I have maybe 1 event a night. Incredible machine.
This is an overly negative response to a genuine solution. There are a million reasons you shouldn't do X or Y.
More than likely GitHub would have to maintain their own internal wallet solution for this, which is a big engineering lift. But we're all just having a discussion.
> you're unfairly conflating things and putting the blame for a lack of care or understanding on tailwind vs on the dev themselves. nothing about tailwind forces you to build inaccessible or "div soup" apps
Hey, that's cool. Does this support conversation lookups? Like, "find this conversation we talked about yesterday"? I built a similar tool to this, although Regent seems much more elegant: https://github.com/divmgl/clancey/