I really hate using VS Code for... well, anything, really.

Thing is, I haven't yet worked out how to set up #NeoVim and #clangd for #PlatformIO and #Arduino projects. I'm guessing the Pico SDK is going to be equally as awkward when I get around to it.

Plus, there's no way to get clangd to properly interpret Psion's old 16-bit DOS-influenced C. If LLVM can't compile it, clangd doesn't seem to care about it.

Me: I should really migrate my Arduino code to the Raspberry Pi Pico C/C++ SDK.
Also me, after working on plptools: I never want to read another line of C++ again.
@thelastpsion Time to reimplement it in Rust.

@jbmorley If I'm rewriting the lot, Go and Zig are also options.

As is Pascal...

@thelastpsion I worked a lot with the Pico SDK (in a commercial setting). I brought a RP2040 to its absolute limits with C.

The Pico-SDK documentation is quite good.
You definitely have more low level control then on arduino.

While C++ is supported for the Pico-SDK, the whole SDK is build around C. There are no classes within the SDK itself. C++ just makes things unnecessary more awkward.