One factor to consider is long term stability, an area where web dev works very differently from embedded devices. Embedded code is often tied to a specific ha

One factor to consider is long term stability, an area where web dev works very differently from embedded devices. Embedded code is often tied to a specific hardware device. I maintain code that was originally written almost 20 years ago. I'm extremely conservative in my technological choices for this reason. Whatever I'm using today needs to keep working if I (or my successors) have to unearth the project in 10 years. And you're right that the vendor-provided tools are often pretty bad, but that's one of the main reasons I personally don't care for IDEs and deep integration with the environment. FZF works reliably everywhere, dummy (non-syntax aware) completion works reliably everywhere etc... Would I be more productive with fancy-pansy code completion? Probably a little bit. But having a simple, agnostic, portable and stable development environment is well worth the trade-off IMO. Not that I think that people are wrong for preferring IDEs, they're just a different set of trade-offs.