Live data from Hacker News

Cursor IDE support hallucinates lockout policy, causes user cancellations

old.reddit.com

191–200 of 635 posts

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#191
post #128

Earlier quoted context omitted.

This is where Kagi’s subscription policy comes in handy. If you don’t use it for a month, you don’t pay for it that month. There is no need to cancel it and Kagi doesn’t have to pay user acquisition costs.

Slack does this as well. It's a genius idea from a business perspective. Normally IT admins have to go around asking users if they need the service (or more likely you have to request a license for yourself), regularly monitor usage, deactivate stale users etc., all to make sure the company isn't wasting money. Slack comes along and says - don't worry, just onboard every user at the company. If they don't log in and…

They mention an user taking an action will be billed. I guess even sending a message or reacting with an emoji would count as taking an action ? Even logging in ?

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#192

Earlier quoted context omitted.

Versioning in source control for even personal projects just got far more important.

It's wild how people write without version control... Maybe I'm missing something.

yeah, "git init" (if you haven't botherered to create a template repo) is not exactly cumbersome.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#193

LLM anything makes me queasy. Why would any self respecting software developer use this tripe? Learn how to write good software. Become an expert in the trade. AI anything will only dig a hole for software to die in. Cheapens the product, butchers the process and absolutely decimates any hope for skill development for future junior developers. I'll just keep chugging along, with debian, python and vim, as I always ha…

Good for you - if that’s what works for you, then keep on keeping on.

Don’t get too hung up on what works for other people. That’s not a good look.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#194

Fingers crossed the users will go left are all the noisy ones. I still enjoy using Cursor but their forum is filled with too many posts about $20 being too expensive or they need to raise caps or Cursor is the worse tool in the world.

[flagged]

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#195
post #37

Earlier quoted context omitted.

It's funny seeing all of the comments trying to blame the users for this screwup by claiming they're using it wrong. It is reddit though, so I guess I shouldn't be surprised.

what is it about reddit that causes this behavior, when they otherwise are skeptical only of whatever the "official story" is at all costs? it is fascinating behavior.

I think it's a combination of oppositional defiant disorder and insufficient moderation.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#196

Earlier quoted context omitted.

That’s a pretty mean spirited way to approach this subject. I think the creators of Redis and Django are very capable and self-respecting software developers.

Is it just me or has there been a wave of delusional people on Hacker News completely neglecting new advancements in technology? The two most common technologies I see having this type of discourse are AI coding and containers. Either everyone here is a low level quantum database 5D graphics pipeline developer with a language from the future that AI hasn't yet learned, or some people are in denial.

I think it’s just backlash against all the AI hype - I get it, im tired of hearing about it too, but - it’s already here to stay, it’s been that way for years now - it’s a normal part of development now for most people, the same as any new tool that becomes the industry darling. Learn to like it or at least learn it, but the reality is here whether you like it or not.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#197

Earlier quoted context omitted.

That’s a pretty mean spirited way to approach this subject. I think the creators of Redis and Django are very capable and self-respecting software developers.

Is it just me or has there been a wave of delusional people on Hacker News completely neglecting new advancements in technology? The two most common technologies I see having this type of discourse are AI coding and containers. Either everyone here is a low level quantum database 5D graphics pipeline developer with a language from the future that AI hasn't yet learned, or some people are in denial.

The gatekeepers are witnessing the gate opening up more and letting more people in and they don't like that at all.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#199

Earlier quoted context omitted.

> You're not supposed to trust the tool This is just an incredible statement. I can't think of another development tool we'd say this about. I'm not saying you're wrong, or that it's wrong to have tools we can't just, just... wow... what a sea change.

> I can't think of another development tool we'd say this about. Because no other dev tool actually generates unique code like AI does. So you treat it like the other components of your team that generates code, the other developers. Do you trust other developers to write good code without mistakes without getting it reviewed by others. Of course not.

"Do you trust other developers to write good code without mistakes without getting it reviewed by others."

Literally yes. Test coverage and QA to catch bugs sure but needing everything manually reviewed by someone else sounds like working in a sweatshop full of intern-level code bootcamp graduates, or if you prefer an absolute dumpster fire of incompetence.

Re: Cursor IDE support hallucinates lockout policy, causes user cancellations

#200
post #41

I just cancelled - not because I thought the policy change was real - but simply because this article reminded me I hadn't used it much this month.

This is where Kagi’s subscription policy comes in handy. If you don’t use it for a month, you don’t pay for it that month. There is no need to cancel it and Kagi doesn’t have to pay user acquisition costs.

Kagi should take it a step further and just charge per search
Post reply on HN