4,891 karma · joined December 11, 2023
When 18-wheelers cross a bridge, it has to be engineered correctly. Unnecessary red-tape happens, but in no way would I want a bridge you "shoot from the hip" carrying my family alongside commercial trucks.
There is probably a configurable way to request suggestions instead of having them automatically pop up - I should configure that.
Back to 1): The type of bug I see most often is where conversation history seems incomplete, and I have trouble rolling back to or even finding a previous point that I am certain existed.
Git shares some features but I think Git was not made for the type of conversational rapid-prototyping LLMs enable. I don't want to be making commits every edit in some kind of parallel-git-state. Cursor's rollback and branching conversations make it easy to backup if a given chat goes down the wrong path. Reapply is tedious since it has to be done one edit at a time - would be nice if you could roll-forward.
I haven't put much thought into what else would be useful, but in general the most value I get from Cursor is simplifying the complex state of branching conversations.
1) The most useful thing about Cursor was always state management of agent edits: Being able roll back to previous states after some edits with the click of a button, or reapply changes, and preview edits, etc. But weirdly, it seems like they never recognized this differentiator, and indeed it remains a bit buggy, and some crucial things (like mass-reapply after a rollback) never got implemented.
2) Adding autocomplete to the prompt box gives me suspicion they somehow still do not understand best practices in using AI to write code. It is more crucial than ever to be clear in your mind what you want to do in a codebase, so that you can recognize when AI is deviating from that path. Giving the LLM more and earlier opportunities to create deviation is a terrible idea.
3) Claude Code was fine in CLI and has a nearly-identical extension pane now too. For the same price, I seem to get just as much usage, in addition to a Claude subscription.
I think Cursor will lose because models were never their advantage and they do not seem to really be thought leaders on LLM-driven software development.
Lots of assumptions about the path to get there, though.
And interesting that he's measuring intelligence in energy terms.
- For complex apps, I love JSX for its ability to distill complexity into simple, discrete components.
- For simple apps, I love HTMX ability to make plain the relationship between raw HTML and API response.
In the MESH examples I see a lot of verbose code that doesn't seem to achieve the simplicity of JSX nor the transparency of HTMX. That said, I certainly don't grok MESH yet so perhaps in a project it would click for me.
2) Hardware optimization (the exact GPU you want may not always be available for some providers)
3) Not subject to price changes
4) Not subject to sudden Terms of Use changes
5) Know exactly who is responsible if something isn't working.
6) Sense of pride and accomplishment + Heating in the winter