Do you have a dumb question that you're kind of embarrassed to ask in the main thread? Is there something you're just not sure about?
This is your opportunity to ask questions. No question too simple or too silly.
Culture war topics are accepted, and proposals for a better intro post are appreciated.
Jump in the discussion.
No email address required.
Notes -
Why do people use Claude? It is slow, dumb, and expensive. Maybe it's somehow magically different on the $200/month plan, but it is basically unusable for me. I am sitting at max usage limits for most of the day. I don't know what I am doing wrong. I really regret getting the subscription. It's fucking down now, too.
I try not to touch the Opus 5 model unnecessarily. I use new chats with fresh context for different features. For bigger projects, I tell Claude to delegate its work to other agents like the good little clanker it is.
Usage limits, for the most part, don't really even exist in Antigravity. I tried Codex, too, but through the API. I was not disappointed and kept upping my balance. I probably ended up spending $30 or so in API fees. I honestly should've gone with my instinct and gotten the ChatGPT subscription instead. I personally found GPT-5.6 Sol to be impressive, though obviously expensive. It was still worth it, since it literally fixed my whole project, did so in a sensible way, and kept running different automated tests to validate everything. Everything just worked perfectly once it was done.
Opus 5's code quality and thinking kinda suck, too. Gemini 3.7 Flash beat it. I had Gemini research and then implement a feature, then I tried to have Claude do the exact same thing starting from the exact same commit and using the exact same prompts. The result was just bad and unimpressive, and it seems it completely misunderstood my prompt. Or, it was just lazy and unambitious.
Fuck Claude. All my homies hate Claude.
EDIT: Deleted and reinstalled the desktop Claude app and... ALL OF MY CHATS ARE GONE. Absolutely asinine way to design an app. Why would deleting the program itself also nuke all of your chat history. That does not make any sense. No other app behaves this way. You routinely have to clean up after deleting a program on Windows because of all the stuff that's left scattered about. Definitely not renewing my subscription after this. What a shitshow. And you'd think that your chats would be stored in the cloud, but no. Because fuck you.
Works for me, I am doing a lot of code generation with it. As for any tool, you have to watch it, and there are cases where it just doesn't work, but in general I think it works fine for me. My job pays for the enterprise subscription, which has $1000 token limit, but I never use that much, maybe $100 or so in tokens per month. But some people do get to the limit (not sure what they do to get there, I just hear them complain about it so I know).
Oh, I always manage to hit the 5-hour token limit within the very first hour of every session. This has honestly made development so needlessly slow and frustrating. Because of this, two days ago I switched over to Codex/ChatGPT.
And I'm already out of tokens. I managed to burn through my entire weekly usage limit in just two days. But I'm not annoyed about it. I actually, finally (!!!!) got everything that I wanted done done. I didn't feel like I was being artificially limited in my usage. It didn't feel arbitrary or money-grubby. It was well forth it.
It's full-on no-code development. Neither I nor anyone else in their right mind would ever willingly write the code I am making these poor clankers write for me. You'd have to be insane. It would take so long, and it would be such an awful experience to even attempt to write it all by hand. You get an AI to do it for you.
But even with AI, and now I'm just ranting, it really does seem like most people (not me) just can't be bothered with it. It's like it's a pain in the ass for them to simply ask the AI to make their shit properly. And so you get "vibecoding" and "vibecoders", who then shit up the internet with their shitty, unoptimized apps.
After working it for a while, I get the impression there's a right way of asking it and a wrong way. And if you ask a wrong way, you get something, but that would be an quite shitty code which sometimes does things that make no sense at all. But if you let it split the task into bite-sized parts and go through them one by one while consistently controlling quality and not letting it do stupid things, you get very decent results. Making it plan things first and only then execute (after you verify and correct the plan) is often the key to getting good results. "Just tell it what to do and it'll do it" is not exactly it - unless you don't care about the quality of the result. Sometimes it works - e.g. for throw-away scripts that it doesn't matter how good/bad the code is, just that it runs, but for code that is going to be maintained it needs more effort.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link