Top
Best
New

Posted by adamfeldman 3 hours ago

Cursor 3(cursor.com)
82 points | 74 commentspage 2
throw03172019 2 hours ago|
I hope we can use it like non-agent developers where code is first class citizen.
Iolaum 3 hours ago||
Looking at the video cursor 3 UI looks very similar to the one I experience using OpenCode :D
whicks 3 hours ago||
This seems like a mix of Claude Code and Superset (https://superset.sh/). Interested to try it out and see how well it performs all the same.
extr 2 hours ago||
What is Cursor doing? They need to relax a little bit. Recently I saw they released "Glass" which WAS here: https://cursor.com/glass, now just redirects to /download.

Is "Cursor 3" == Glass? I get they feel like their identity means they need to constantly be pushing the envelope in terms of agent UX. But they could stand to have like an "experimental" track and a "This is VS Code but with better AI integration" track.

leerob 2 hours ago|
Glass was a codename while the UI was in early alpha with testers. It redirects to download now because there is no special link anymore. It's just part of Cursor 3 itself.
maipen 2 hours ago||
So funny , I remember their talk about re-imagining their editor for the future of agents. They end up copying codex gui lol.

These AI companies are running out of ideas, and are desperate. I can't imagine investing in companies that are 3 month behind open source alternatives, and their target audience being the most experimental kind there is.

Looks pretty though.

wiradikusuma 2 hours ago||
Maybe I'm old, but I only recently started using Gemini to assist me in coding. Now it seems everyone is heading to giving agents to do the full-blown coding. I guess if the result code is good, it doesn't matter who's coding (me or AI).

But are they affordable already for developers who don't earn a Silicon Valley salary? Developers in 3rd world countries?

seamossfet 2 hours ago|
I'm not convinced people who are doing real work on production applications with any sizable user base is writing code through only agents. There's no way to get acceptable code from these models without really knowing your code base well and basically doing all the systems thinking for the model.

Your workflow is probably closer to what most SWEs are actually doing.

ryandrake 7 minutes ago|||
You really need to keep them on a tight leash, stop and correct them when they start screwing up, and then the remaining 90% of the work starts after they say their done, where you need to review/refactor/replace a lot of what they produced.

The only way you're going to let an agent go off on its own to one-shot a patch is if your quality bar is merely "the code works."

nprateem 12 minutes ago||||
Not true. As long as you don't blindly accept their garbage and keep things behind sensible interfaces so you can reimplement if necessary, and have good tests you're fine
simplyluke 2 hours ago|||
This, at least for me, has changed in the past six months. Which is the same thing people were saying in the months prior to that, so I will accept some eye rolls. But at least for our pretty large monorepo opus + a lot of engineering work on context got us to a point where a large portion of our engineers are doing most of their work with agents first and a lot of back and forth + smaller hand edits.
kypro 11 minutes ago||
Agreed. The size of the repo isn't a limiting factor anymore. It's more about the type of change.

Agents today can generate solid code even for relatively complex requirements. However, they don't always make the right trade-offs.

Just because something works doesn't mean it scales. It doesn't mean it can handle unexpected user input. It doesn't mean it's easily extensible.

Today engineers really just need to define those high-level technical requirements.

simplyluke 6 minutes ago||
> Today engineers really just need to define those high-level technical requirements.

At least within our company, this is quickly becoming what it means to be a software engineer.

vially 2 hours ago||
Thought I'd give it a try and installed the latest version. Application crashes at startup on Linux (Wayland) with: "The window terminated unexpectedly (reason: 'crashed', code: '139')". Probably yet another instance of developers mostly testing and doing quality assurance on macOS/Windows.
jonasnelle 2 hours ago||
Hey, sorry about that! Some AUR packages share cursor in a way that isn't forward+backwards compatible across releases. We recommend using our official AppImage from https://cursor.com/download Alternatively, please use a different AUR package that doesn't have these issues https://aur.archlinux.org/packages/cursor-nightly-bin
slopinthebag 2 hours ago||
I really dislike this push away from augmentation and towards agents. I get that people want to be lazy and just have the LLM do all of their work, but using the AI as an augmentation means you are the driver and can prevent it from making mistakes, and you still have knowledge of the codebase. I think there is so much more we could be doing in the editor with AI, but instead every company just builds a chatbot. Sigh.
weli 2 hours ago||
Stop fucking my shit up please
AdrienPoupa 33 minutes ago||
My exact reaction when they override my cmd+e shortcut and change the default layout every two months :)
reasonableklout 1 hour ago||
Looks like the editor is still there, and the revamped UI is a new window you can open on the side.
acedTrex 2 hours ago|
So they are just turning into another vibe code slop app?

At least before they were tangentially still an actual developer tool, standard vsc windows, the code was the point etc.

Now they offer really nothing interesting for professionals.

tredre3 41 minutes ago||
> Now they offer really nothing interesting for professionals.

That's a curious statement given that what they're doing is just becoming more like Claude Code, which seems extremely popular on this forum.

cyral 2 hours ago||
All the VS code stuff is literally still there