Hacker News new | ask | show | jobs
by mountainriver 363 days ago
What??? It’s literally the worst interface

Do you not want to edit your code after it’s generated?

3 comments

I'm running terminal in one window with AI interaction and then VS Code with project on same directories so I can see via color coding updated or new files to review in the IDE.

How do you interact with your projects?

How is that better than running your AI interaction in a dedicated toolpane/subwindow directly inside your IDE?

The Chat panel in VS Code has seen a lot of polish, can display full HTML including formatting Markdown nicely, has some fancy displays for AI context such as file links, supports hyperlinks everywhere, and has fancy auto-complete popups for things like @ and # and / mentioned "tools"/"agents"/whatever. Other VS Code widgets can show up in the Chat panel, too. The Chat Panel you can dock in either sidebar and/or float as its own window.

A terminal can do most of those things too, with effort and with nothing quite like the native experience of your IDE and its widgets. It seems like a lesser experience than what VS Code already offers, other than you only have one real choice for AI assistant that supports VS Code's Chat panel (though you still have model choice).

I run aider in VSCode terminal so that I can fix smaller lint errors myself without another AI back-and-forth.
this is demonstrably worse than cursor
Sure, in VS Code. Or Xcode. Or IntelliJ/GoLand/RubyMine.
...if your IDE doesn't have a terminal then it isn't an IDE.
The "old wisdom" on comp/lang.perl.misc, when new people asked what was the best IDE to Perl programming, was "Unix".

You get both editors to choose from, vi _and_ emacs! All the man pages you could possibly want _and_ perldocs! Of _course_ as a Perl newbie you'll be able to fall back on gdb for complicated debugging where print statements no longer cut it.

I have a whole other screen for my terminal(s). The IDE already has enough going on in it.
Then you are not impeded from editing your code because it was written through a terminal process, which seems to be OP's contention.
why wouldn't you want the diffs in the IDE? Its richer and you can do more with them