The recent release of Cursor version 0.43 has been reckless. I think it is that an insufficiently tested version was pushed directly to users.
The update has been plagued with issues and big changes, including frequent server unresponsiveness and an incomplete, poorly implemented “Composer” feature. Critical functionalities like document and codebase referencing are missing, severely impairing productivity. Yesterday, my workflow was almost entirely halted as I constantly retried requests or waited for sluggish responses. The shallow context provided by Composer led to subpar outputs, forcing me to repeatedly regenerate results, wasting time and undermining the value of my Pro subscription.
I firmly demand compensation for Pro users and an official apology. Going forward, Cursor must commit to releasing only stable versions to its user base. Pro users should not bear the burden of testing your product.
I agree with this as well. There should be a stable channel and a beta channel for Cursor IDE. Updates to the stable version should only be released after thorough testing. Users who want to try out new features can opt to use the beta version.
Just to play devil’s advocate, we’re paying to fund an ambitious project that’s still in beta. Yes, as a paying customer I expect a working product, and that will require a personal cost/benefit analysis.
But these guys are still in early innings and working hard to make a magic product to democratize development for all. At least that’s how I see. SO I will cut them some slack, as long as the intent is good and we’re all getting value.
Agree with the sentiment though, sacrificing quality for speed is not a winning strategy when it can affect someone’s day with lost work.
Agree, while yes, it does bug and pissed a lot of people, including me. As a 2-year continuous pro user, I find it a bit annoying. But, to be honest, it’s still beta for this whole project, so I am totally into the idea that we’re in the funding stage.
The Cursor is great. It has so much potential to be the next generation or redefine how we develop software. With a small team and so much ambition, It’s fine for them to make mistakes, but as long as they listen to their customer and aim for good intentions.
Make mistakes and correct them. That’s to develop.