> I just like doing it in code... really dead simple: { R1-2 D1-A }
Yeah, and I can (used to) code troff/nroff for document and book production. I'm not totally sure that GUI WYSIWYG interfaces are better. I always ran WordPerfect with Reveal Codes open. But the whole point, from Parc to Lisa to Mac, has been to get away from mental re-mapping into FORTRAN-like gibberish. And generally the Mac developers have been ahead of the curve.
My Pspice does not deal directly with package and layout. I think that is a new frill. But somewhere a few releases back they got a GUI schematic editor. Yes, I do miss numbering the nodes on a napkin and typing it in. Not because it is fun, but because the GUI auto-numbers nodes behind the scene and I don't know what node is what. Does not matter until the netlist parser barfs an error: it tells me what node is no-go, but there is no way to find a node-number on the GUI. I have to flip through the card-deck (OK, line-ASCII file) and figure what part is on that node, etc.
Just like modern document tools "help" the user, it seems to me that a good electronics editor/stimulator ought to do a lot more than Pspice or TINA or WorkBench does.