4 ms·

I feel like GUIs these days cater too much to novice users. Obviously the old-school terminal/no-graphics style is pretty dated, but I have yet to see a nicely

by qu4z-2 13y ago

I feel like GUIs these days cater too much to novice users. Obviously the old-school terminal/no-graphics style is pretty dated, but I have yet to see a nicely integrated solution with the advantages of GUIs and the power of the cli.

pjmlp 13y ago
Maybe, but I don't feel that way. I do enjoy the power of the CLI for automation and pipelining of commands and build scripts. However I am a visual guy and also enjoy the power of IDEs when coding. So I rather use the GUI and make use of the CLI when required, than the other way around. This was exactly how one would use Amiga OS. Spend most of the time in Workbench and use Amiga DOS when required to do so. Or even the old Mac OS, where a terminal was a third party application. There was no command line, only GUI.
- nmcfarl 13y ago
  So after your first comment I was wondering what GUI gives you as far as tools in an IDE that you couldn't have with curses style terminal-based interface. Emacs (and vi) do a wide assortment of refactorings, auto-completions, multipaned outputs, large scale cut and pastes etc. I couldn't think of anything that actually needed graphics. Given that i couldn't think of any reason why an IDE needed to be a GUI. That is to say I can see people preferring the look, or the use of a pointing device, but I couldn't figure out any coding features that where actually GUI-only. You have any I couldn't think of?
  - pjmlp 13y ago
    Code navigation, able to represent visually references between modules, packages, binary files. Quite handy to navigate across large code bases, typical in enterprise environments. Another nice feature is the ability to see graphical representations of data structures. Specially handy for list and tree based structures. Design and prototyping of user interfaces.

4 ms·

I feel like GUIs these days cater too much to novice users. Obviously the old-school terminal/no-graphics style is pretty dated, but I have yet to see a nicely

by qu4z-2 13y ago

pjmlp 13y ago
Maybe, but I don't feel that way. I do enjoy the power of the CLI for automation and pipelining of commands and build scripts. However I am a visual guy and also enjoy the power of IDEs when coding. So I rather use the GUI and make use of the CLI when required, than the other way around. This was exactly how one would use Amiga OS. Spend most of the time in Workbench and use Amiga DOS when required to do so. Or even the old Mac OS, where a terminal was a third party application. There was no command line, only GUI.
- nmcfarl 13y ago
  So after your first comment I was wondering what GUI gives you as far as tools in an IDE that you couldn't have with curses style terminal-based interface. Emacs (and vi) do a wide assortment of refactorings, auto-completions, multipaned outputs, large scale cut and pastes etc. I couldn't think of anything that actually needed graphics. Given that i couldn't think of any reason why an IDE needed to be a GUI. That is to say I can see people preferring the look, or the use of a pointing device, but I couldn't figure out any coding features that where actually GUI-only. You have any I couldn't think of?
  - pjmlp 13y ago
    Code navigation, able to represent visually references between modules, packages, binary files. Quite handy to navigate across large code bases, typical in enterprise environments. Another nice feature is the ability to see graphical representations of data structures. Specially handy for list and tree based structures. Design and prototyping of user interfaces.