IDEs, UNIX, AND THE LEGACY WORKFLOW THAT NEVER WENT AWAY

Words of Wisdom are dispensed in the article

I have a workflow consisting of

• screen
• bash or one of
• csh
• ksh
• zsh
• vim or
• vim.motif
• function 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 "$_"; }
• gcc
• g++
• asm
• ln
• go from golang
• lsd
• ncdu

These choices are deliberate. I want and demand the fastest programming ENV: which follow the UNIX principle & KISS

quotes

tl;dr*

Unix already solved many IDE problems decades ago using small cooperating tools instead of one large application.

• bash
• coreutils
• less
• tmux
• nvialready 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 predictable

sources:

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.txt

https://go.dev/doc/install

https://go.dev/doc/tutorial/getting-started

#programming #UNIX #gcc #g++ #asm #ln #golang #lsd #ncdu #ncurses #BSD #freeBSD #ghostBSD #openBSD #Linux #OpenSource #POSIX

New title screens. Animated!

See them live in web emulator: https://smol.p1x.in/assembly/game12/game12.html

Or MS-DOS: https://smol.p1x.in/assembly/game12/game12.com

p.s. the actual game is in alpha stage, middle of implementing core mechanisms. stay tooned.

#GameDev #IndieDev #x86 #Assembly #asm #PixelArt

Cortex Labs (bootdisk and MS-DOS)

TOTAL OPCODE INSTANCES: 2404
UNIQUE OPCODES: 56
BINARY SIZE: 14522 bytes

#GameDev #IndieDev #x86 #Assembly #asm