I'm not a super experienced hardware guy, altho I do quite a few bits and bobs, and I always found the graphical entry of schematic... silly.
As a lifelong software developer, entering schematics with little boxes and lines seems roughly equivalent to try to do serious programming using one of these languages where you drag&drop boxes around, used to teach beginners.
Having a way to have a description language for schematics makes a lot of sense; HDL/Verilog exists so you don't have to use the graphical editor for describing your h264 encoder for example. Likewise, Excel source code isn't made in a graphical editor either.
Now I'm not sure the python scripting example given on the page show the potential as it's best as it tries to highlights a bit too much the 'programming' bit; also some sort of 'good practice' would need to evolve; like grouping parts together, labeling, comments etc.
As a lifelong software developer, entering schematics with little boxes and lines seems roughly equivalent to try to do serious programming using one of these languages where you drag&drop boxes around, used to teach beginners.
Having a way to have a description language for schematics makes a lot of sense; HDL/Verilog exists so you don't have to use the graphical editor for describing your h264 encoder for example. Likewise, Excel source code isn't made in a graphical editor either.
Now I'm not sure the python scripting example given on the page show the potential as it's best as it tries to highlights a bit too much the 'programming' bit; also some sort of 'good practice' would need to evolve; like grouping parts together, labeling, comments etc.