As someone who works on a "modern" low-code platform, your comment reads like someone who hasn't used the state of the art. I've had to manipulate actual XML m

As someone who works on a "modern" low-code platform, your comment reads like someone who hasn't used the state of the art. I've had to manipulate actual XML maybe once in a year; and usually because of an insane legacy DB schema. I'm sure it happens but I don't see it much. In fact XML isn't a huge factor. You know it's there, but you don't really care. Also they aren't "always Eclipse based", lately they are browser-based, which will irritate people just as much (but the web is something more of a "growth market" than Java IDEs). Modern platforms have built-in testing suites. I have seen individual rules or UIs with hundreds of tests. (Process models remain hard to test, though, much to everyone's frustration) The plugin problem is real, even in modern platforms. That said, pick any platform - the web browser, an IDE, even a game engine. For a lot of users, entirely dependent on plugins. It's just part of life.