I was using CDT until WFH started in March. At the time Remote System Explorer appeared to be dead-ish so I went with VSCode. Eclipse CDT is extremely tedious t

I was using CDT until WFH started in March. At the time Remote System Explorer appeared to be dead-ish so I went with VSCode. Eclipse CDT is extremely tedious to configure the include paths for because they all have to be entered one by one in a text box. VSCode has a remote system extension and include paths can be entered en masse into a JSON file. I've used both with embedded projects that involve cross compilers. VSCode doesn't know MIPS processors are a thing so some of my linux driver code has unwarranted squiggles. For Eclipse the same constructs are handled by the methods it uses for any code. Eclipse supports its superior features with a lot of reindexing. VSCode supports its features with glorified searches.