I have a different take on this. Full disclosure, yes I am a boomer.
I am in an interesting position. I get to design software, scripts, RTL that goes into chips, and boards to test the chips, both before (emulation via FPGA) and after (validation tests) the chips are fabricated.
Pictures are great for some forms of communication. Definitely with other humans. Even sometimes with the computer (e.g. schematics, when you have to).
But I far prefer text for doing actual work. Scripts that convert schematic netlists into textual things that can be tested, diffed, viewed in a different fashion, saved to a code repository? Yes, I make and use these on a regular basis.
If you've ever tried to do an optical compare on schematic pages by holding two of them up on a window, hoping that the paper is thin enough you can see differences, you'll understand.
Now, schematics map directly to hardware. They have some utility, and it is worthwhile to create tools to let me view/diff/version control them in a textual way.
Labview? Simulink? Not so much. Not at all. I have _never_ found the utility of labview to be worth using enough to worry about how to check for differences and version control it. I fucking hate it. Simulink is probably marginally more useful, but not worth spending money on, IMO.
Other programming tools? Same. I suppose I could imagine a world where the stored diffs weren't terrible and there was a nice visual way to do useful comparisons that wouldn't let you easily miss important differences, but that's probably the same world where nobody makes Excel spreadsheet errors, either, and I'm not going to hold my breath waiting for that world to show up.
I'll probably be the last adopter, too, for any such technology. Converting schematics to text so that I can write scripts to reason about them has saved my bacon so many fucking times that I am disinclined to go the other direction at all. I have zero FOMO on this purported trend.