Hacker Newsnew | past | comments | ask | show | jobs | submit | ochronus's commentslogin

Doesn't match my personal experience over a handful of iPhone generations. I know, anecdotal only, but still.

I've also never had a 'slowdown' nor have I ever had the purported "all the charging cables crumble" problem people keep claiming Apple has materials engineering problems for.

I wonder if people are just too sensitive to a handful of milliseconds of delay and calling it "slowdown" and didn't grow up on an era of metal that took minutes to do simple tasks.



I think Liquid Glass is a general UX/Product blunder, not a deliberate evil masterplan to force users to buy new phones.

But the result is the same. And it's not the first time (see: the slowdown without user consent).

I don't think they are clueless, but rather, struggling. Being an AI provider is a money burner, and they probably don't have enough fuel for the fire anymore, so they are trying things to squeeze more $$$ and limit usage at the same time.


I don't really expect a company run by radical effective altruists / ai doomers to have good business sense.

They had a decent product and squandered a lot of dev goodwill almost overnight.


I see your point, but I'd be surprised if they'd lose a significant user base in the end; the hype is just way too high


Yeah, claude code is mostly unusable at this point. It's been in a constant decline for a good 1-2 months. It's more like a scam now.


What are the biggest problems you've seen? Is it mostly related to limits for the subscription plans?

Within my circles (mostly big enterprises), I see more and more of my friends using Claude, and spending money on it, so they must be getting some sort of value out of it. For my uses, I've also been successful with Claude Code, though someone else is paying for my tokens.


Yes, it's related to the limits of the subscription plans. 2ish months ago the same sub started hitting limits earlier and earlier on very similar tasks/codebases. Then they said, Oh, sorry, it was a caching bug, now it's fixed. It wasn't. Then a couple more bugs. Still no fix. Recently they announced "doubling the limits" (made possible by the Grok deal) - still hitting limits super fast compared to how it used to be 2+ months ago. Moreover, the models got somewhat dumber and slower, too.


Also, they seem to ignore auto mode, seizing on any reason to stop, and sometimes just stopping despite saying they’re proceeding with something.

Basically, ongoing enshittification.


Hence the only other path: slow, constant enshittification of the models' performance


As predicted by many. The math is, as usual, mathing.


No, it's not, except for a small percentage of the userbase.


Haha, right, just like the recent uncommunicated changes to limits, cache, etc.


This is awesome! Thank you for building it!


You are welcome. Would love to hear your feedback.



Pretty sure I was hit by that caching bug because there was a few hours where I immediately hit my session limit and then shortly after I hit it again all while the system wasn't even working because of downtime, likely due to the increased token usage...

But I think it only lasted for a short period of time.


Hmm, the bug I hit lasted for days and burned through my credits/limits/tokens like crazy, consistently. It's gone after the last update.


Ok, so this is how they try to compensate for their messed up month of bugs (insane token burn)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: