Well then there is not even a single reason for switching from VS Code for a normal dev. When I tried it in Debian with a normal laptop, it continuously caused freezing, because it kinda throttled the integrated graphics.
I really wish there is an editor that support vscode’s devcontainer like containerisation, but open source. I really don’t like doing it manually. Too much effort for something that can be autonated.
The tooling around AI should be to improve the quality of the programmer. Not to write the code for the programmer.
For example if you ask an agent how to scale things well, and best practices in architecture, it will have a lot of resources on it. But that does not mean the code it will produce when you ask it to write a programme will consider and include the best practices it gave you in a separate question. That is the ‘intelligence’ part that LLMs cannot have. If you ask a it to do a certain way it will create it. Context tries to address this by prompting the user to give more, but that is not persistent.
This is exactly why senior devs finding LLMs works for them, because they know ‘how’ to do it, and they explicitly state it. But at the same time junior devs feel they think the code written by LLM is the ‘best’ way so solve a problem and superior in quality, even if it is not, because they don’t know any better.
Tooling should be able to help the developers improve their knowledge and skill on ‘how’ to do it. Instead it always focus on writing the code. I want to add that I’m not talking about algorithms. But every aspect of coding, in which the programmer needs to know ‘how’ to do it.