#nodemon — Public Fediverse posts

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

nodemon -e "s sh" --exec ./run.sh

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

nodemon -e "s sh" --exec ./run.sh

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

nodemon -e "s sh" --exec ./run.sh

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

nodemon -e "s sh" --exec ./run.sh

Using #GNU as Assembler (not Assembly, but the Assembler) and ld Linker to spit out a working BMP gradient image.

Yeah, you read it right. I'm not using #Assembly to produce an image. I'm, instead, using Assembler directives and macros during compile-time to generate a binary file that happens to be a valid image (BMP) file.

File: tonishing.s (GNU Assembly file)

width = 320
height = 240
area = width * height
_begin:
    .ascii "BM"
    .int fileSize
    .int 0
    .int (_rasterdata - .)

_infoheader:
    .int infoheaderSize
    .int width     # width
    .int height    # height
    .short 1       # planes
    .short 24      # bitcount
    .int 0         # compression
    .int 0         # imagesize
    .int 11811     # xpixperm
    .int 11811     # ypixperm
    .int 0         # colorsused
    .int 0         # colorsimp

infoheaderSize = (. - _infoheader)

_rasterdata:
    n=area+1
    .rept height
        .rept width
            byten=((n*255)/area)&0xFF
            rn=(192*byten)/255
            gn=(64*byten)/255
            bn=(128*byten)/255
            .byte rn,gn,bn
            n=(n-1)
        .endr
    .endr

fileSize = (. - _begin)

#!/bin/sh
clear
rm astonishing.bin
rm tonishing.o
as tonishing.s --64 -o tonishing.o
# The pun is _astonishingly_ intended.
strip -R .comment -R .note.gnu.property tonishing.o
ld -n -x -s -N --oformat binary --unique=.note.gnu.property -o astonishing.bin tonishing.o
magick identify -verbose astonishing.bin

nodemon -e "s sh" --exec ./run.sh

One day I'm tinkering with #Ruby and #JS one-liners and their quirks, the other day I'm tinkering with CPU registers and instructions via #GNU #Assembly. Guess I'm into the latter, now (as strange as it may sound, I'm using a #nodemon + #Makefile pipeline to re-compile and re-run Assembly every time I change the #code, thus turning Assembly into a live-coding platform of sorts)

One day I'm tinkering with #Ruby and #JS one-liners and their quirks, the other day I'm tinkering with CPU registers and instructions via #GNU #Assembly. Guess I'm into the latter, now (as strange as it may sound, I'm using a #nodemon + #Makefile pipeline to re-compile and re-run Assembly every time I change the #code, thus turning Assembly into a live-coding platform of sorts)

One day I'm tinkering with #Ruby and #JS one-liners and their quirks, the other day I'm tinkering with CPU registers and instructions via #GNU #Assembly. Guess I'm into the latter, now (as strange as it may sound, I'm using a #nodemon + #Makefile pipeline to re-compile and re-run Assembly every time I change the #code, thus turning Assembly into a live-coding platform of sorts)

One day I'm tinkering with #Ruby and #JS one-liners and their quirks, the other day I'm tinkering with CPU registers and instructions via #GNU #Assembly. Guess I'm into the latter, now (as strange as it may sound, I'm using a #nodemon + #Makefile pipeline to re-compile and re-run Assembly every time I change the #code, thus turning Assembly into a live-coding platform of sorts)

One day I'm tinkering with #Ruby and #JS one-liners and their quirks, the other day I'm tinkering with CPU registers and instructions via #GNU #Assembly. Guess I'm into the latter, now (as strange as it may sound, I'm using a #nodemon + #Makefile pipeline to re-compile and re-run Assembly every time I change the #code, thus turning Assembly into a live-coding platform of sorts)

I was today years old when I discovered Nodemon. It gives you really nice hot reloading for Node. Quite useful for APIs or Discord bots. Probably more too, but that's what I use it for. I just added something like:
"mon": "nodemon index.js"
to my Discord bot's "scripts" section of package.json, so I can run `npm run mon` and now it reloads whenever I save a file.
https://www.npmjs.com/package/nodemon
#JavaScript #Discord #DiscordJS #Nodemon #node

I was today years old when I discovered Nodemon. It gives you really nice hot reloading for Node. Quite useful for APIs or Discord bots. Probably more too, but that's what I use it for. I just added something like:
"mon": "nodemon index.js"
to my Discord bot's "scripts" section of package.json, so I can run `npm run mon` and now it reloads whenever I save a file.
https://www.npmjs.com/package/nodemon
#JavaScript #Discord #DiscordJS #Nodemon #node

I was today years old when I discovered Nodemon. It gives you really nice hot reloading for Node. Quite useful for APIs or Discord bots. Probably more too, but that's what I use it for. I just added something like:
"mon": "nodemon index.js"
to my Discord bot's "scripts" section of package.json, so I can run `npm run mon` and now it reloads whenever I save a file.
https://www.npmjs.com/package/nodemon
#JavaScript #Discord #DiscordJS #Nodemon #node

I was today years old when I discovered Nodemon. It gives you really nice hot reloading for Node. Quite useful for APIs or Discord bots. Probably more too, but that's what I use it for. I just added something like:
"mon": "nodemon index.js"
to my Discord bot's "scripts" section of package.json, so I can run `npm run mon` and now it reloads whenever I save a file.
https://www.npmjs.com/package/nodemon
#JavaScript #Discord #DiscordJS #Nodemon #node

I was today years old when I discovered Nodemon. It gives you really nice hot reloading for Node. Quite useful for APIs or Discord bots. Probably more too, but that's what I use it for. I just added something like:
"mon": "nodemon index.js"
to my Discord bot's "scripts" section of package.json, so I can run `npm run mon` and now it reloads whenever I save a file.
https://www.npmjs.com/package/nodemon
#JavaScript #Discord #DiscordJS #Nodemon #node