home.social

#sizecoding — Public Fediverse posts

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

  1. :neofox_facepalm:
    I messed up my #sizecoding Makefile. Only noticed now when I compiled "wake up!", a 16 byte intro. The "stats" make target was showing the disassembly's size, not the binary size. I was afraid I was running out of space with my circle drawing code, but I'm only at 52 bytes instead of 900-ish. :neofox_laugh_sweat:
    cc: #theWorkshop

  2. :neofox_facepalm:
    I messed up my #sizecoding Makefile. Only noticed now when I compiled "wake up!", a 16 byte intro. The "stats" make target was showing the disassembly's size, not the binary size. I was afraid I was running out of space with my circle drawing code, but I'm only at 52 bytes instead of 900-ish. :neofox_laugh_sweat:
    cc: #theWorkshop

  3. :neofox_facepalm:
    I messed up my #sizecoding Makefile. Only noticed now when I compiled "wake up!", a 16 byte intro. The "stats" make target was showing the disassembly's size, not the binary size. I was afraid I was running out of space with my circle drawing code, but I'm only at 52 bytes instead of 900-ish. :neofox_laugh_sweat:
    cc: #theWorkshop

  4. :neofox_facepalm:
    I messed up my #sizecoding Makefile. Only noticed now when I compiled "wake up!", a 16 byte intro. The "stats" make target was showing the disassembly's size, not the binary size. I was afraid I was running out of space with my circle drawing code, but I'm only at 52 bytes instead of 900-ish. :neofox_laugh_sweat:
    cc: #theWorkshop

  5. :neofox_facepalm:
    I messed up my #sizecoding Makefile. Only noticed now when I compiled "wake up!", a 16 byte intro. The "stats" make target was showing the disassembly's size, not the binary size. I was afraid I was running out of space with my circle drawing code, but I'm only at 52 bytes instead of 900-ish. :neofox_laugh_sweat:
    cc: #theWorkshop

  6. Frigging Hell Mood did it again:

    cwd
    Z: add al,5
    X: int 10h
    out 61h,al
    test cl,ch
    mov ax,0x0c82
    loopnz X
    jmp short Z

    I dare you to run this in DOSBox!
    #demoscene #sizecoding

  7. Frigging Hell Mood did it again:

    cwd
    Z: add al,5
    X: int 10h
    out 61h,al
    test cl,ch
    mov ax,0x0c82
    loopnz X
    jmp short Z

    I dare you to run this in DOSBox!
    #demoscene #sizecoding

  8. Frigging Hell Mood did it again:

    cwd
    Z: add al,5
    X: int 10h
    out 61h,al
    test cl,ch
    mov ax,0x0c82
    loopnz X
    jmp short Z

    I dare you to run this in DOSBox!
    #demoscene #sizecoding

  9. Frigging Hell Mood did it again:

    cwd
    Z: add al,5
    X: int 10h
    out 61h,al
    test cl,ch
    mov ax,0x0c82
    loopnz X
    jmp short Z

    I dare you to run this in DOSBox!
    #demoscene #sizecoding

  10. Frigging Hell Mood did it again:

    cwd
    Z: add al,5
    X: int 10h
    out 61h,al
    test cl,ch
    mov ax,0x0c82
    loopnz X
    jmp short Z

    I dare you to run this in DOSBox!
    #demoscene #sizecoding

  11. @s0ftwave1662 Here i have posted some sample code for a 256-byte demo running on Linux. The source code contains very few comments.

    gitlab.com/metagrowing/demos

    32 Bit Assembler code that is able to run on 64 Bit Linux Distro.

    “Graphics” here refers to the ability of ESC sequences to change colors in the Linux terminal.

    “Sound” means the hardware beeper or the notification sound of a desktop manager.

    #sizecoding #MountainBytes

  12. @s0ftwave1662 Here i have posted some sample code for a 256-byte demo running on Linux. The source code contains very few comments.

    gitlab.com/metagrowing/demos

    32 Bit Assembler code that is able to run on 64 Bit Linux Distro.

    “Graphics” here refers to the ability of ESC sequences to change colors in the Linux terminal.

    “Sound” means the hardware beeper or the notification sound of a desktop manager.

    #sizecoding #MountainBytes

  13. @s0ftwave1662 Here i have posted some sample code for a 256-byte demo running on Linux. The source code contains very few comments.

    gitlab.com/metagrowing/demos

    32 Bit Assembler code that is able to run on 64 Bit Linux Distro.

    “Graphics” here refers to the ability of ESC sequences to change colors in the Linux terminal.

    “Sound” means the hardware beeper or the notification sound of a desktop manager.

    #sizecoding #MountainBytes

  14. @s0ftwave1662 Here i have posted some sample code for a 256-byte demo running on Linux. The source code contains very few comments.

    gitlab.com/metagrowing/demos

    32 Bit Assembler code that is able to run on 64 Bit Linux Distro.

    “Graphics” here refers to the ability of ESC sequences to change colors in the Linux terminal.

    “Sound” means the hardware beeper or the notification sound of a desktop manager.

    #sizecoding #MountainBytes

  15. @s0ftwave1662 Here i have posted some sample code for a 256-byte demo running on Linux. The source code contains very few comments.

    gitlab.com/metagrowing/demos

    32 Bit Assembler code that is able to run on 64 Bit Linux Distro.

    “Graphics” here refers to the ability of ESC sequences to change colors in the Linux terminal.

    “Sound” means the hardware beeper or the notification sound of a desktop manager.

    #sizecoding #MountainBytes

  16. Trying to learn some #DOS #sizecoding during lunch break. First mistake that qualifies as a happy little accident. :neofox_uwu:

    echo aACgB7ATzRCquM3M9+eI0PbgicOI8PbgAcOD+z596bAP6+U= | base64 -d > a.com
    dosbox a.com

    cc: #theWorkshop #theFoundry

  17. Trying to learn some #DOS #sizecoding during lunch break. First mistake that qualifies as a happy little accident. :neofox_uwu:

    echo aACgB7ATzRCquM3M9+eI0PbgicOI8PbgAcOD+z596bAP6+U= | base64 -d > a.com
    dosbox a.com

    cc: #theWorkshop #theFoundry

  18. Trying to learn some #DOS #sizecoding during lunch break. First mistake that qualifies as a happy little accident. :neofox_uwu:

    echo aACgB7ATzRCquM3M9+eI0PbgicOI8PbgAcOD+z596bAP6+U= | base64 -d > a.com
    dosbox a.com

    cc: #theWorkshop #theFoundry

  19. Trying to learn some #DOS #sizecoding during lunch break. First mistake that qualifies as a happy little accident. :neofox_uwu:

    echo aACgB7ATzRCquM3M9+eI0PbgicOI8PbgAcOD+z596bAP6+U= | base64 -d > a.com
    dosbox a.com

    cc: #theWorkshop #theFoundry

  20. Trying to learn some #DOS #sizecoding during lunch break. First mistake that qualifies as a happy little accident. :neofox_uwu:

    echo aACgB7ATzRCquM3M9+eI0PbgicOI8PbgAcOD+z596bAP6+U= | base64 -d > a.com
    dosbox a.com

    cc: #theWorkshop #theFoundry

  21. New video: Let's Code MS DOS: 0x37 Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    YouTube: Let's Code MS DOS: 0x37 Rainbow Surf Analysis
    youtu.be/FGf2LEAbdSg
    Makertube: makertube.net/w/hpE75cfisPMrmZ

    #letscode #msdos #sizecoding #demoscene

  22. New video: Let's Code MS DOS: 0x37 Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    YouTube: Let's Code MS DOS: 0x37 Rainbow Surf Analysis
    youtu.be/FGf2LEAbdSg
    Makertube: makertube.net/w/hpE75cfisPMrmZ

    #letscode #msdos #sizecoding #demoscene

  23. New video: Let's Code MS DOS: 0x37 Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    YouTube: Let's Code MS DOS: 0x37 Rainbow Surf Analysis
    youtu.be/FGf2LEAbdSg
    Makertube: makertube.net/w/hpE75cfisPMrmZ

    #letscode #msdos #sizecoding #demoscene

  24. New video: Let's Code MS DOS: 0x37 Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    YouTube: Let's Code MS DOS: 0x37 Rainbow Surf Analysis
    youtu.be/FGf2LEAbdSg
    Makertube: makertube.net/w/hpE75cfisPMrmZ

    #letscode #msdos #sizecoding #demoscene

  25. New video: Let's Code MS DOS: 0x37 Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    YouTube: Let's Code MS DOS: 0x37 Rainbow Surf Analysis
    youtu.be/FGf2LEAbdSg
    Makertube: makertube.net/w/hpE75cfisPMrmZ

    #letscode #msdos #sizecoding #demoscene

  26. New video for Patrons: Let's Code MS DOS 0x37: Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    patreon.com/posts/lets-code-ms

    #retrocomputing #demoscene #sizecoding #msdos #letscode

  27. New video for Patrons: Let's Code MS DOS 0x37: Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    patreon.com/posts/lets-code-ms

    #retrocomputing #demoscene #sizecoding #msdos #letscode

  28. New video for Patrons: Let's Code MS DOS 0x37: Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    patreon.com/posts/lets-code-ms

    #retrocomputing #demoscene #sizecoding #msdos #letscode

  29. New video for Patrons: Let's Code MS DOS 0x37: Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    patreon.com/posts/lets-code-ms

    #retrocomputing #demoscene #sizecoding #msdos #letscode

  30. New video for Patrons: Let's Code MS DOS 0x37: Rainbow Surf Analysis

    This year's Revision demoparty had a surprising winner in the 256 byte compo. It was Rainbow Surf by Plex/BionFX and it is only 16 bytes long. That is short, very short. In fact, here is the code: c4 04 48 ab 26 03 45 ae 26 03 05 c1 e8 02 eb f2. Let's dissect it!

    patreon.com/posts/lets-code-ms

    #retrocomputing #demoscene #sizecoding #msdos #letscode

  31. To my #sizecoding bubble: How can I get some crappy random numbers on x86 IBM PC platforms? I am thinking about reading out a clock port... Or is there a minimal pseudeo RNG algorithm that takes only a handful of bytes? Doesn't have to be a GREAT random number source...

  32. To my #sizecoding bubble: How can I get some crappy random numbers on x86 IBM PC platforms? I am thinking about reading out a clock port... Or is there a minimal pseudeo RNG algorithm that takes only a handful of bytes? Doesn't have to be a GREAT random number source...

  33. To my #sizecoding bubble: How can I get some crappy random numbers on x86 IBM PC platforms? I am thinking about reading out a clock port... Or is there a minimal pseudeo RNG algorithm that takes only a handful of bytes? Doesn't have to be a GREAT random number source...

  34. To my #sizecoding bubble: How can I get some crappy random numbers on x86 IBM PC platforms? I am thinking about reading out a clock port... Or is there a minimal pseudeo RNG algorithm that takes only a handful of bytes? Doesn't have to be a GREAT random number source...

  35. To my #sizecoding bubble: How can I get some crappy random numbers on x86 IBM PC platforms? I am thinking about reading out a clock port... Or is there a minimal pseudeo RNG algorithm that takes only a handful of bytes? Doesn't have to be a GREAT random number source...

  36. A little Linux demoscene starter application I've written (C + GLSL):

    A C demo template. It makes an executable that's 7kb and can be shared to other systems.

    I've use my superformula SDF code from years on back.

    Uses _start syscalls and eschews the standard library in order to be that size.

    It also only uses libGL and libX11, that's it.

    That said: I have no idea how people manage to make 4k demos, ha.

    #demoscene #sizecoding #creativecoding

  37. A little Linux demoscene starter application I've written (C + GLSL):

    A C demo template. It makes an executable that's 7kb and can be shared to other systems.

    I've use my superformula SDF code from years on back.

    Uses _start syscalls and eschews the standard library in order to be that size.

    It also only uses libGL and libX11, that's it.

    That said: I have no idea how people manage to make 4k demos, ha.

    #demoscene #sizecoding #creativecoding

  38. A little Linux demoscene starter application I've written (C + GLSL):

    A C demo template. It makes an executable that's 7kb and can be shared to other systems.

    I've use my superformula SDF code from years on back.

    Uses _start syscalls and eschews the standard library in order to be that size.

    It also only uses libGL and libX11, that's it.

    That said: I have no idea how people manage to make 4k demos, ha.

    #demoscene #sizecoding #creativecoding

  39. A little Linux demoscene starter application I've written (C + GLSL):

    A C demo template. It makes an executable that's 7kb and can be shared to other systems.

    I've use my superformula SDF code from years on back.

    Uses _start syscalls and eschews the standard library in order to be that size.

    It also only uses libGL and libX11, that's it.

    That said: I have no idea how people manage to make 4k demos, ha.

    #demoscene #sizecoding #creativecoding

  40. A little Linux demoscene starter application I've written (C + GLSL):

    A C demo template. It makes an executable that's 7kb and can be shared to other systems.

    I've use my superformula SDF code from years on back.

    Uses _start syscalls and eschews the standard library in order to be that size.

    It also only uses libGL and libX11, that's it.

    That said: I have no idea how people manage to make 4k demos, ha.

    #demoscene #sizecoding #creativecoding