IDEs, UNIX, AND THE OLD WORKFLOW THAT NEVER WENT AWAYWords of Wisdom are dispensed in the articleI have a workflow consisting ofscreenbash or one ofcshkshzshvim orvim.motiffunction third(){ awk '{if (NR%3==0){print "\033[32m" $0 "\033[0m"} else{print}}'; }function psgrep() { ps axuf | grep -v grep | grep "$@" -i --color=auto; }function mkcd(){ [ ! -z "$1" ] && mkdir -p "$1" && cd "$_"; }gccg++asmlngo from golanglsdncduThese choices are deliberate. I want and demand the fastest programming ENV: which follow the UNIX principle & KISSquotestl;dr*Unix already solved many IDE problems decades ago using small cooperating tools instead of one large application.bashcoreutilslesstmuxnvialready form a complete and focused development environment for many Unix workflows.The shell becomes the workspace, the terminal manages sessions, and the editor remains small and predictablesources:man sh(1)man ls(1)man coreutils(1)man less(1)man screen(1)man tmux(1)man vim(1)https://www.gnu.org/software/screen/https://repo.or.cz/code-notes.git/blob_plain/HEAD:/notes/Unix_As_An_IDE.txthttps://go.dev/doc/installhttps://go.dev/doc/tutorial/getting-started#programming #UNIX #gcc #g++ #asm #ln #golang #lsd #ncdu #ncurses #BSD #freeBSD #ghostBSD #openBSD #Linux #OpenSource #POSIX
