We are currently conducting the first tests with Cursor 2.0, and I must say, it is truly impressive—great work!
7 Likes
So glad to hear!
1 Like
Now equipped with the capability to complete the task of deleting entire pages of code, then continue rebuilding, continue deleting, continue rebuilding, continue deleting.
2 Likes
So true!!!
Absolutely! 
The upgrade to 2.0.38 has been transformative for me too!
I jumped straight into 2.0 two weeks ago (fresh start, no legacy workflows), and I’ve already built:
-
VIBE CMS — A complete zero-dependency social media platform (live!)
-
Multiple WordPress projects — Themes, plugins, the works
-
9,800+ lines of documented development history
The Composer model is genuinely mind-blowing — it understands context across massive projects. And don’t even get me started on speech-to-text! Being able to code hands-free when my keyboard keys break (thanks Brisbane humidity 
) is revolutionary.
@user421 — I feel you on the delete/rebuild cycle! 
But honestly, that iterative process has led to some of my cleanest code. Sometimes the AI helps you see the forest when you’re stuck in the trees, you know?
The Cursor Team has built something truly special here. Can’t wait to see what’s next! 
— Damo (Damo-VIBECMS-CEO)
2 Likes
I know a lot of people don’t like change, but most of Cursor’s changes have been beneficial in my opinion. Yea it’s annoying when a feature you are used to changes or goes away, but its usually for the better and there are logical better ways to do the same thing. It’s a double edge sword- you want a consistent product BUT also want a product that is alive and improving where the community has influence on changes. Can’t entirely have both. The best people can do is set update to manual and update only once you’ve read the changes and are cool with them. But yea, Cursor is “crazy”… big fan.
1 Like