Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "GUI Programming Introduction - Computerphile" video.

7:53 Don’t forget, server programs are also event-driven, and they often don’t have any kind of user interface at all. Instead, they are responding to events received over client connections.
8
@CTimmerman Who might be running GUI frontends. Or they might not.
4
@kc9scott Emacs, on the other hand, can go full graphical. You can even have clickable buttons in the middle of a text buffer.
3
6:20 There is another way to write a command-line program, and that is to get its inputs from command-line arguments. Options passed by keyword can typically be specified in any order. This is typically more flexible than asking the user to type input lines.
3
@kc9scott This is why I have an Emacs window always open. The scratch buffer is a handy place to compose long command lines before turning them loose on bash.
2
@stefanluginger3682 IDEs tend to be inflexible in their support for different build systems. In Open Source software, there are a great variety of build systems in use. That’s why I avoid IDEs, and just use a powerful editor like Emacs. That way, it can drive any build system that the project might be using.
2
@keinunvergebenesaliasgefunden Regular Emacs does all that just fine.
1
GUIs are great for running multiple terminal windows. Copy and paste works nicely for command lines, which is something you cannot do with GUI operation sequences.
1
@lincolnsand5127 Yeah, but copy and paste doesn’t work between them.
1
Those were block-mode terminals. Proper GUIs can do things like change parts of the window in response to input elsewhere (e.g. enable/disable one option based on the setting of another, update a live preview image etc), while those terminals could not do any such thing.
1