Ask HN: Are new AI code editors adding superficial value?
Specifically referring to Cursor and Melt. It seems to be the rage among the bay area AI community but they're basically just VS Code skins. Im pretty happy with VS Code both features-wise and UX, but I think now is the golden opportunity to fundamentally rethink the craft & work of human coding and build a new UI/App from scratch. Including NOT building on Electron..
17 comments
[ 3.5 ms ] story [ 37.5 ms ] thread- Human collaboration is a first class citizen if not the main design pillar. Instead of having add extensions for git, github etc. these need to be baked into the IDE. In-line blame, graph/UI for git history, diffs, team code editing etc.
- Basic code assistance utilities: Intellisense, Linting, Static Analysis, Formatting, Docstring Preview, Type Hinting, Dependency graphs, Code Metadata should again be key features that ships with the IDE as opposed to being enabled through extensions.
- Modern AI based code assistance: in-line code assistive comments based on review of what you wrote, tab autocomplete (this is covered well by the AI code editors/extensions), automatic documentation
- Implementation in C/Rust with effective/efficient usage of compute resources. Zed does do this
- Baking in project management/collab from JIRA/Linear: This would be the only way to keep human engineers collaboration not woefully slower than AI 'engineers' who would automatically bug fix, push, do PRs, review PRs etc.
- Environment, Containers and package management baked in with nice UX. Python (the most popular language today) has a very fractured ecosystem with conda, venv, virtualenv, pipenv etc. Replace these with using uv+ruff (as they are FOSS) baked into the IDE.
Somewhere out there is a far more 'native' way of coding with the AI together, where the LLM constantly sees the entire code base as you code; you don't code 'into the codebase', but you code 'into the LLM'. Hard to explain what I mean here...
The problem is if the LLM actually understands nuances and dependencies in the codebase structure.
For some languages and clear frameworks maybe so, but in many cases it could still misinterpret. Doable though imho to improve it.
There are some open source competitors coming out that I'm watching but Cursor is still top for me.
For the first example, in a recent architecture task, I took ~6 hours researching options, and would have taken ~2-3 hours implementing my version. It took ~20 minutes with Cursor given I was able to give it my desired implementation very clearly and it applies the code immediately. I take most of those 20 mins reviewing the code, not even writing!
For the second, I mean stuff like renaming many variables that have similar but not identical names, or rewriting the way functions are defined/documented so it's the same for all, or adding type hints to all functions. Stuff that you need to typically do 1 by 1 and can't do Ctrl+Shift+F or multiline edit for. With Cursor, I make the first change and it simply knows I want to do something similar for the rest of my file/workspace. I just press tab 10 times and all the changes are done. From ~30-40 minutos to ~1 minute on a task that happens often.
Both of those have made much more productive (easily worth the price). As a distant third, having the ability to have Claude + Search has also been pretty useful.
I do think that there is a danger to the tool. It is great for senior programmers, but I think a quite harmful poison for juniors. While I go from large amounts of research to a bit of code reviewing, I think a junior will likely go from 0 research to direct implementation to 20 hours of bug squashing because they trusted it blindly.
I'm confused why people are giddy over Cursor given how polished Zed is
https://github.com/zed-industries/zed/discussions/6562#discu...
Cursor I think has taken off because it couldn't be easier to try out.
Take out 90% of the windows users from bothering to try the software and that is really going to hurt people talking up the software online.