←back to thread

432 points tosh | 1 comments | | HN request time: 0s | source
Show context
tyoma ◴[] No.39995915[source]
I’ve used aider to understand new codebases using technologies I don’t know and it did a fantastic job; much faster than grep/find + google.
replies(1): >>39995997 #
fyrn_ ◴[] No.39995997[source]
To be fair in a world of good LSP impls, grep/find are really primative tools to be using. Not saying this isn't better then a more sophisicated editor setup, just that grep and find are a _really_ low bar
replies(4): >>39996106 #>>39996629 #>>39997312 #>>40027408 #
shadowgovt ◴[] No.39996106[source]
When we reach that world, let me know. I'm still tripping over a "python-lsp-server was simply not implemented async so sometimes when you combine it with emacs lsp-mode it eats 100% CPU and locks your console" issue.
replies(2): >>39996914 #>>39999527 #
1. fyrn_ ◴[] No.39999527[source]
If emacs hard blocks on LSP requests, that may be on emacs as well. I recomemd you try ruff-lsp, although it does not iver everything and is more for linting, it's higb quality