home.social

#asm — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #asm, aggregated by home.social.

  1. #ASM ist nur einmal im Jahr.
    #ASM26
    Alternativlose Trinkmaßnahme. 😁

  2. Anyone got links to a good tutorial on systems programming for M-series based #MacOS ? I eventually want to get into #ARM64 based assembly #ASM , but I'm happy starting with #C / #Cpp

  3. Anyone got links to a good tutorial on systems programming for M-series based #MacOS ? I eventually want to get into #ARM64 based assembly #ASM , but I'm happy starting with #C / #Cpp

  4. Anyone got links to a good tutorial on systems programming for M-series based #MacOS ? I eventually want to get into #ARM64 based assembly #ASM , but I'm happy starting with #C / #Cpp

  5. Anyone got links to a good tutorial on systems programming for M-series based #MacOS ? I eventually want to get into #ARM64 based assembly #ASM , but I'm happy starting with #C / #Cpp

  6. Anyone got links to a good tutorial on systems programming for M-series based #MacOS ? I eventually want to get into #ARM64 based assembly #ASM , but I'm happy starting with #C / #Cpp

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

    gnu.org/software/screen/

    repo.or.cz/code-notes.git/blob

    go.dev/doc/install

    go.dev/doc/tutorial/getting-st

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

  8. 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)

    gnu.org/software/screen/

    repo.or.cz/code-notes.git/blob

    go.dev/doc/install

    go.dev/doc/tutorial/getting-st

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

  9. 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)

    gnu.org/software/screen/

    repo.or.cz/code-notes.git/blob

    go.dev/doc/install

    go.dev/doc/tutorial/getting-st

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

  10. 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)

    gnu.org/software/screen/

    repo.or.cz/code-notes.git/blob

    go.dev/doc/install

    go.dev/doc/tutorial/getting-st

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

  11. 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)

    gnu.org/software/screen/

    repo.or.cz/code-notes.git/blob

    go.dev/doc/install

    go.dev/doc/tutorial/getting-st

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

  12. Some #PremierLeague’s Clubs have shown interest in #ASMonaco’s striker Folarin #Balogun for the summer transfer window. #transfers #ASM

  13. Some #PremierLeague’s Clubs have shown interest in #ASMonaco’s striker Folarin #Balogun for the summer transfer window. #transfers #ASM

  14. Some #PremierLeague’s Clubs have shown interest in #ASMonaco’s striker Folarin #Balogun for the summer transfer window. #transfers #ASM

  15. #ASMonaco are set to trigger the option to buy (€11M) to sign Ansu #Fati on a permanent deal from #Barça. Contract until 2030. #transfers #FCB #ASM

  16. #ASMonaco are set to trigger the option to buy (€11M) to sign Ansu #Fati on a permanent deal from #Barça. Contract until 2030. #transfers #FCB #ASM

  17. #ASMonaco are set to trigger the option to buy (€11M) to sign Ansu #Fati on a permanent deal from #Barça. Contract until 2030. #transfers #FCB #ASM

  18. New title screens. Animated!

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

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

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

  19. New title screens. Animated!

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

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

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

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

  20. New title screens. Animated!

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

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

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

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

  21. New title screens. Animated!

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

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

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

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

  22. New title screens. Animated!

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

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

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

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

  23. Cortex Labs (bootdisk and MS-DOS)

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

  24. Cortex Labs (bootdisk and MS-DOS)

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

    #GameDev #IndieDev #x86 #Assembly #asm

  25. Cortex Labs (bootdisk and MS-DOS)

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

    #GameDev #IndieDev #x86 #Assembly #asm

  26. Cortex Labs (bootdisk and MS-DOS)

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

    #GameDev #IndieDev #x86 #Assembly #asm

  27. Cortex Labs (bootdisk and MS-DOS)

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

    #GameDev #IndieDev #x86 #Assembly #asm

  28. @shriramk transpiling is such an interesting can of worms. Intuition suggests there shouldn’t be much different about adding #scheme at the end of the #c -> #asm -> machine code chain, but it also seems like C is a somewhat arbitrary detour, when scheme already looks a lot like the AST.

  29. @shriramk transpiling is such an interesting can of worms. Intuition suggests there shouldn’t be much different about adding #scheme at the end of the #c -> #asm -> machine code chain, but it also seems like C is a somewhat arbitrary detour, when scheme already looks a lot like the AST.

  30. @shriramk transpiling is such an interesting can of worms. Intuition suggests there shouldn’t be much different about adding #scheme at the end of the #c -> #asm -> machine code chain, but it also seems like C is a somewhat arbitrary detour, when scheme already looks a lot like the AST.

  31. @shriramk transpiling is such an interesting can of worms. Intuition suggests there shouldn’t be much different about adding #scheme at the end of the #c -> #asm -> machine code chain, but it also seems like C is a somewhat arbitrary detour, when scheme already looks a lot like the AST.

  32. @shriramk transpiling is such an interesting can of worms. Intuition suggests there shouldn’t be much different about adding #scheme at the end of the #c -> #asm -> machine code chain, but it also seems like C is a somewhat arbitrary detour, when scheme already looks a lot like the AST.