> The bane of embedded development is awful tooling and people who aren't very good programmers inventing abstractions that do more harm than good. Use VSCode.

> The bane of embedded development is awful tooling and people who aren't very good programmers inventing abstractions that do more harm than good. Use VSCode. It's not great, but it's SOOOO much better than everything else in the embedded space (that doesn't cost $100K+) that it's ridiculous. As for programmers, any programmer of talent decamped from the embedded world to anything else. As long as semiconductor companies refuse to pay real salaries, this will continue. > Write tooling in a portable language that can produce proper binaries. Preferably statically linked binaries so that at least you do not have to waste time wondering why your tooling doesn't work. Write tooling in Rust or Go. No. Just no. Installing random crap in any language on my computer is where things fail. Use a bloody container. To contain the mess, it's what I have to do anyway. For the love of all that is holy and unholy, distribute a container. This is the kind of scenario that containers were MADE for--lots of random tools that need to be version locked and only upgraded as a single unit.