Hacker News new | past | comments | ask | show | jobs | submit login

My background is heavily biased towards C++ but I don't really feel like you can make it work in VS Code without understanding, at minimum, where your clangd is actually located. The C++ plugins don't install what you need where you need them, and the launch.json really does not just work. My ex was unable to set up a C++26 toolchain for VS Code because without my help he couldn't configure the settings to connect to the right version of clang tools, and I don't think he ever got the GDB debug adapter working at all.



One of the definite positives of AI is that kind of stuff is now fairly easy to solve.

It surfaces a lot of the ways people found to fix those problems in forums/git issues/random blogs that were hard to track down past google spam.

And it tends to list the possible fixes in a nice little bullet point list of things to try to get everything working.


> One of the definite positives of AI is that kind of stuff is now fairly easy to solve.

I agree that 'AI' feels like a fancier/faster 'Google' (I've done the thing where I find a Github issue from 4 years ago that explains the problem), but when we will see a local AI agent that looks at your current configuration/issue and solves the problem for you, and then gives you a summary of what it did?


open-interpreter has been around for a while by this point.


I get that and I also couldn’t get a boilerplate Vue/TypeScript library project started using AI - bear in mind any guide I could find was at least a year old and by now things have changed enough that none of them work either, but it was overall frustrating for something that should be simple




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: