There's an important distinction between 2 categories in architecture diagrams:

1. Free-form. You have an image of what it should look like. It's precise. An algorithm won't be able to get it right.

2. Structured. You just want to represent the relationships in a clean way, and there's a hundred ways to do that acceptably.

Code/text can never replace the former, and free-form ones are always going to have its place. It's too black & white to say all diagrams should be code or not code.

I'm one the authors of a new text-to-diagram tool, and I wouldn't recommend it for all use cases. Example here of free-form vs structured: https://d2lang.com/tour/future#layouts

We made Terrastruct so you can mix-and-match both, with GUI or code: https://app.terrastruct.com/diagrams/2034296181